There's no universal PDF size limit for permit review. Your local portal controls the cap, and limits vary widely by jurisdiction and file type. Check your portal's checklist first; if you can't find a number, keep each trade file comfortably under common municipal limits, split by discipline, and include a sheet index so reviewers can navigate your set without confusion.
TL;DR:
- Portal limits range from 50 MB per trade file to 1 GB per file, with caps set per file, trade, or full submission; check local rules.
- Without a published cap, target under 50 MB per trade; export vector PDFs at 1:1 scale, flattened and unlocked, with searchable TrueType text.
- Reduce PDF size with vector output; if scanning is necessary, use monochrome line art at 300 ppi maximum and split oversized sets into labeled volumes.
- On resubmittals, preserve filenames and sheet order, add new sheets at the end or follow portal revision rules, and update any required index.
Table of Contents
- Common municipal file-size limits and what to expect
- How to prepare PDFs for electronic plan review
- Naming, splitting, and resubmittal rules
- Reducing file size without losing scale or legibility
- What reviewers actually check and why submissions get rejected
- How ShearWise Pro produces permit-ready structural PDFs
- Reviewer usability matters more than squeezing out megabytes
- Generate reviewer-ready shear wall reports without the guesswork
- FAQ
- Sources
Common municipal file-size limits and what to expect
Every jurisdiction sets its own ceiling, and the range is wide. Some cities cap individual trade files at 50 MB, while others allow much larger uploads for a full plan set.
Here's what we've seen across municipal submittal guides:
- 50 MB per trade file is a common cap for drawing files in systems like Philadelphia's eCLIPSE, which also requires a separate sheet index spreadsheet.
- 200 MB per file appears in San Diego's digital plan submission requirements, paired with page-size and optimization guidance.
- 250 MB per file shows up in several regional examples for combined architectural and structural sets.
- 500 MB per file is the ceiling in Seattle's plan review guidance, which also recommends grouping multiple sheets into a single discipline PDF.
- 1 GB per file is permitted under Phoenix's SHAPE PHX submittal requirements, one of the more generous caps we've found.
The pattern matters as much as the numbers. Some portals cap per file, others cap per trade (architectural, structural, mechanical, electrical, plumbing each counted separately), and a few set a total upload ceiling across the whole submission. A 300-page structural set with embedded raster images can blow past a 50 MB cap fast, while the same set as clean vector output might sit well under 20 MB.
If your portal's limit isn't published anywhere obvious, treat 50 MB per trade file as your conservative working target. That number clears the strictest systems we've reviewed and still leaves room for drawings with moderate raster content. When a single discipline's drawings won't fit under that target even after cleanup, split the set into logical volumes rather than pushing one oversized file through the upload process.
How to prepare PDFs for electronic plan review
Reviewers don't just check whether your file opens. Plan check software renders, measures, and annotates your PDF, and that only works reliably when the file follows a few technical rules.
- Export native vector PDFs directly from your CAD or design software instead of printing to a raster image. Vector output keeps linework sharp at any zoom level and usually produces a smaller file than a scanned equivalent.
- Plot at 1:1 scale, never "scale to fit." Reviewers measure dimensions directly off the PDF, and a scaled-to-fit export throws every measurement off.
- Flatten the file before export. Flattening merges layers and removes interactive objects like comments and editable fields, which keeps the file stable inside plan check software.
- Leave the file unlocked. Password protection and encryption block the automated tools reviewers use to stamp, annotate, and route your submission.
- Use TrueType fonts, not SHX or other CAD-native font types, so text stays searchable rather than becoming an unreadable image of text.
- Add bookmarks or a sheet index when your portal requests one. A 40-sheet structural set without navigation forces a reviewer to scroll manually through every page to find the foundation plan.
- Keep page size and orientation consistent across each file, and confirm your sheet numbering and title block sit in the same spot on every page.
Pro Tip: Export a test PDF and open it in a different viewer than the one you used to create it: fonts, line weights, and scale errors often only show up once you're outside your native software.
Scale errors deserve extra attention because they're easy to miss on screen but obvious the moment someone measures the drawing. A partner guide on scaling PDF drawings walks through how estimators catch doubled quantities caused by scale mismatches, and the same mismatches that throw off a takeoff will throw off a reviewer's dimension check.
If you're submitting signed structural calculations alongside your drawings, the same flattening rule applies to signature pages. Our guide to electronically signing structural calculations covers how to keep a signed PDF flattened and unlocked without breaking the signature's validity.
Naming, splitting, and resubmittal rules
File-size limits get most of the attention, but naming and resubmittal rules cause just as many rejections. These rules exist because plan check systems track documents by filename across review cycles, and a renamed or reordered file breaks that tracking.
- Split by discipline when one trade's drawings exceed your target file size: architectural, structural, mechanical, electrical, and plumbing each become their own PDF rather than one combined file.
- Split by volume when even a single discipline's set is too large, using clear labels like "Structural Vol 1 of 2" rather than arbitrary sheet ranges.
- Avoid special characters in filenames (no slashes, ampersands, or symbols), and keep names concise with a discipline prefix such as "S-" for structural or "A-" for architectural.
- Preserve filenames exactly on resubmittal. Kitsap County's instructions and similar municipal guides warn against renaming files between review cycles because reviewers compare the new file against the old one by name.
- Don't reorder or insert sheets in the middle of a revised set. Add new sheets at the end or follow your portal's specific revision numbering instead.
- Keep a sheet index (often XLSX) updated alongside your PDF when the portal requires one, so the index and the actual sheet order always match.
Getting these administrative details right the first time avoids a second round of plan check comments that have nothing to do with your actual design. Our breakdown of common shear wall plan check comments covers a few of the recurring fixes we see tied to filename and sheet-order mistakes.
Reducing file size without losing scale or legibility
Shrinking a PDF is only useful if the drawing stays readable and stays to scale. A few settings make the biggest difference.
- Stick with vector output wherever your software allows it. Vector linework compresses efficiently and stays sharp regardless of zoom level.
- If you must rasterize, use monochrome 1-bit depth for line drawings and cap resolution at 300 ppi for scanned pages. Color or grayscale scans at high resolution are the single biggest cause of bloated plan PDFs.
- Compress images with lossless methods for linework (LZW works well for monochrome bitmaps) and reserve lossy JPEG2000 compression for photographic content only, so drawing legibility isn't sacrificed to save space.
- Remove embedded or unused fonts and metadata before export. Many CAD programs embed full font sets and layer metadata that add weight without adding value to the reviewer.
- Flatten before compressing, not after. Flattening removes the interactive objects that often carry the most hidden file weight.
- Use your PDF software's optimization preset for line drawings rather than a general photo-optimized preset, since photo presets tend to degrade thin linework.
A flattened, vector-based structural PDF is typically a fraction of the size of the same drawing set scanned at high resolution, according to Seattle's plan review guidance, which recommends vector-preferred export specifically to keep file sizes manageable.
If you've applied every optimization step and still exceed your portal's cap, splitting into logical volumes is the standard fallback used across the jurisdictions we've reviewed, not a sign you've done something wrong.
What reviewers actually check and why submissions get rejected
Reviewers run through a fairly consistent set of checks before they even look at your design, and most rejections trace back to one of a handful of recurring issues.
- Scale and dimensions: reviewers measure drawings directly off the PDF, so a scale-to-fit export or inconsistent page size fails immediately.
- File integrity: locked, encrypted, or unflattened files often won't process through plan check software at all.
- Readable linework and text: raster scans with poor resolution or CAD-native fonts that didn't convert to searchable text slow reviewers down and invite rejection.
- Navigation aids: missing bookmarks or a missing sheet index on a large set makes a reviewer's job harder and can trigger an incomplete-submission flag.
- Administrative matching: filenames that don't match a prior submittal, reordered sheets, or missing attachments from the checklist are common, entirely avoidable rejection causes.
If a submission does get rejected, preserve your original files and fix only the specific pages the reviewer flagged. Resist the urge to reorganize the whole set, since that's often what causes the resubmittal itself to get bounced. Keeping naming and order consistent across cycles, a point we cover in more detail in our streamlined plan review submittals guide, tends to shorten the number of review cycles overall.
How ShearWise Pro produces permit-ready structural PDFs
Our report export is designed around a checklist that reviewers use. Each report keeps a live, editable project file separate from the PDF submitted, so a flattened, optimized export goes to the portal while the working file stays editable for the next revision.
Shear wall calculations, wall line layouts, hold-down forces, and transfer strap summaries are organized into labeled report sections with bookmarks and a sheet index built in, so a reviewer can jump directly to key sections without scrolling through many pages. Filenames remain consistent across exports, which is important when a resubmittal requires matching the original file name.
You can see what this looks like in practice in our sample ShearWise report, and our tutorials walk through the export workflow step by step.
Reviewer usability matters more than squeezing out megabytes
A file that's 10 MB smaller than it needs to be doesn't speed up approval. A file with consistent naming, a working sheet index, and preserved order across resubmittals does, because it cuts the back-and-forth that eats review cycles.
We'd rather see a structural PDF sit comfortably under a portal's cap with full bookmarks and a clean index than shaved to the smallest possible size at the cost of navigation. Keep a flattened copy for submittal and an editable master for corrections. When a reviewer comment comes back, you want to fix the actual page, not rebuild the whole export from scratch.
— Evalin
Generate reviewer-ready shear wall reports without the guesswork
Our focus is on organizing shear wall calculations for 1-story and 2-story wood-framed buildings into clean, reviewer-friendly PDF reports. Rather than relying on general structural software, those pieces are built into every export by default.
- Export flattened, optimized PDF reports with bookmarks and a sheet index already in place.
- Keep wall lines, openings, hold-down forces, and transfer straps organized in one report structure instead of scattered across loose calculation sheets.
- Start with the Three-Report Trial at no cost, then move to Professional Monthly at $29 per month or Professional Annual at $250 per year once you're ready for ongoing projects.
Try the three-report trial on your next project and see what a reviewer-ready PDF looks like before you commit to a plan.
FAQ
Is there a single maximum PDF size for permit submissions?
No single maximum applies everywhere. Limits range from 50 MB per trade file in some systems to 1 GB per file in others, like Phoenix's SHAPE PHX guidance, so your local portal's checklist is the only reliable source.
What's a safe target file size if my portal doesn't list one?
Aim to keep each trade file under 50 MB, the common cap used in systems like Philadelphia's eCLIPSE. That target clears most stricter portals and still leaves room for moderate raster content.
Should I flatten my PDF before submitting it for permit review?
Yes, flattening is standard practice and often required. It merges layers, removes editable comments, and keeps the file stable inside the plan check software reviewers use, as described in municipal guides like Kitsap County's submittal instructions.
Can I rename my files when resubmitting revised plans?
Generally, no. Most portals, including Kitsap County's, instruct applicants to preserve original filenames and sheet order on resubmittal so reviewers can track changes between cycles without confusion.
Why does my drawing need to be plotted at 1:1 scale?
Reviewers measure dimensions directly off the PDF, so a "scale to fit" export throws off every measurement. Phoenix's EPR requirements specifically call for 1:1 plotting for this reason.
Sources
- Requirements for Digital Plans & Documents | City of San Diego Official Website
- SHAPE PHX EPR submittal requirements (City of Phoenix)
- Construction and Inspections: PDF submission guidance (Seattle DPD)