Document file size basics for PDFs and images

Ten pages of typed text may be 400 KB. Ten pages of phone photos inside a PDF may be 40 MB. Page count misleads applicants who think “short application” means “small upload.” The bytes live in embedded images, font subsets, and uncompressed streams.

QuickConvert tackles size in the browser with PDF Compress, Image Compress, and structural tools like PDF Split.

Measure before you panic

Check file properties on disk. Divide megabytes by page count for a per-page budget. Portals stating “5 MB max” reward knowing which pages are photos.

Born-digital text PDFs barely shrink because text is already efficient. Scanned PDFs shrink when raster images inside re-encode. Compression does not replace splitting a 200-page scan when the portal wants multiple attachments.

Read the guide on reducing PDF size for preset thinking. Balance quality until stamps remain readable.

Emailing loose JPGs? Compress before you build PDF. A fat photo album turned into Images to PDF stays fat unless you shrink sources first.

HEIC may look small on phone but fails portals—convert with HEIC to JPG then compress.

Resolution caps

Downscaling beats crushing JPEG quality. Resize long edge to what the viewer needs. Screens rarely need 6000 px width.

When total size must drop but every page matters, split with PDF Split into two uploads if the portal allows multiple files. When one attachment is mandatory, compress until artifacts appear, then reconsider scan DPI.

Office exports via Office to PDF inherit chart images. Delete unused sheets before export.

PDF Watermark adds little size. Embedded thumbnails and duplicate fonts hurt more. Cleanup tools live outside QuickConvert for exotic PDFs.

Server compressors see your medical PDFs. Browser compress keeps bytes local. Same for image compress during tax season.

Visa packet over limit: compress, then split exhibits if allowed. Homework PDF: photograph at lower resolution, images-to-PDF, compress. Board deck: export charts as balanced PDF compress preset.

Link through PDF under upload size limit for portal math.

Why did compress do nothing? Likely text-only PDF.

Will compress hurt OCR? Heavy compress on scans can. OCR before aggressive squeeze.

Can I compress twice? Possible but quality drops. Start balanced.

Do zips count toward email limits? Yes—total attachment bytes matter.

Is PNG smaller than JPG for photos? Usually no. PNG is for graphics and transparency.

Should I delete fonts? Do not manually—compress handles embedded images.

What about linearized PDF? Fast web view is unrelated to megabytes.

Does split change quality? No—splits copy pages.

Create a one-page PDF for colleagues: photos should be under two megabytes before they hit Images to PDF. Link PDF Compress and the upload-limit guide. Most “my PDF is too big” tickets are uncompressed scans from the copier downstairs.

Put the byte limit from the portal in the subject line when you forward instructions so nobody guesses wrong.

Copier defaults at 600 dpi are why “one page” blows the cap; ask facilities for a 200 dpi profile for email-bound scans.

Slack and chat uploads

Chat apps downscale previews but full downloads still count limits on the receiving server. Compress before upload even when the thumbnail looks fine.

Mobile scanner apps

Scanner apps love 400 dpi colour for receipts. Switch to grey and 200 dpi for text invoices. Colour is for expense photos with highlighted rows, not every PDF.

Engineering drawings

CAD exports with embedded raster views can dwarf photos. Flatten in CAD or export a scaled JPEG view for reviewers who only need to see shapes.

Archives versus email

Keep a lossless archive on disk; email a compressed derivative. Students submitting theses should not confuse what they store with what the portal accepts.

Measuring progress

Log before-and-after megabytes when coaching colleagues. A chart on the wiki showing “38 MB to 4 MB” teaches better than repeating “use compress.”

Cross-link reduce PDF size and PDF under upload size limit in your internal memo so curious readers learn the theory behind the button they clicked.

Weekend on-call engineers appreciate when attachments include both megabyte count and page count in the ticket body so they pick compress versus split immediately.

Insurance adjusters emailing photo claims should batch compress in the browser before Images to PDF so one claim equals one attachment under carrier rules.

Receipt photos in expense apps should be greyscale unless colour proves VAT eligibility; grey PDFs compress further with less visible artefact on thermal paper text.

Legal discovery ZIPs sometimes explode when someone nested lossless TIFF scans; extract, compress sensibly, and re-archive with a manifest listing megabytes per Bates range.

HR onboarding packets mixing born-digital policies and signed scan photos should list which sections are searchable text versus image-only so new hires know where to copy-paste answers.

Conference Wi-Fi uploads fail when PDFs exceed venue limits; compress in the hotel room on your laptop before the submission site times out at midnight local.

Title companies receiving merged closing PDFs should split oversized e-recording packets with PDF Split when county portals cap pages per submission.

Volunteer organisations emailing newsletter PDFs should teach writers that one full-bleed hero photo can dominate the megabyte budget for the entire issue.

Small business owners uploading loan packets should check cellular upload limits, not only desktop email caps.

Real estate agents should compress disclosure photo PDFs before texting them; cellular MMS limits are stricter than inbox rules.

Departments publishing open-data PDFs should also publish CSV when the table is the product; bytes matter for civic hackers too.