Productivity & Workflows

Build a Portfolio PDF Under an Upload Limit

An image-heavy portfolio has to fit a 10 MB form without looking terrible. Here is where the megabytes go and what to cut first.

Written against the Aug 1, 2026 release·what has changed since

8.4 MBLOSSLESSRASTERDPI + qualityMEASUREDcompare bytes

Twenty-four full-bleed images, sixty-two megabytes, and an application form that accepts ten. The instinct is to compress until it fits and hope nobody looks closely. There is a better order, and it starts before any compression at all.

Cut before you compress

Six weak pages removed is a quarter of the file gone at zero cost to quality, and a stronger portfolio besides. Reviewers are not counting pages. Decide what stays while the images are still at full quality, because a decision made after compression is a decision made on degraded evidence.

Resize the images, not just the PDF

Images to PDF embeds your PNG and JPEG bytes into the document. Page fitting changes the display size, not the source pixels, so a 6000 pixel wide JPEG stays a 6000 pixel wide JPEG inside a page that shows it at a quarter of that. This is the single biggest reason portfolio PDFs are enormous.

Export the images at a sensible size from whatever made them first: roughly 2000 pixels on the long edge is generous for a page somebody will read on a laptop. Then build the document with A4 or Letter pages and Contain fitting, unless you genuinely want full-bleed edges cropped, in which case Cover is the one that does it.

The tool embeds what you give it: Nothing in the conversion step recompresses your photographs, and that is deliberate: a tool that silently degraded your work would be worse. It does mean the input size is the output size, so the saving has to happen before the import or in a later compression pass.

Then compress, in two stages

  1. 1

    Lossless first

    Compress PDF in Lossless cleanup rewrites the structure and preserves everything visible. On an image-heavy file the saving is usually small, because the weight is in the pictures rather than the plumbing.

  2. 2

    Measure, then decide

    The export report gives before and after byte counts. If lossless got you to eleven megabytes, one more step will do. If it got you to fifty-eight, the images are the problem and you should go back and resize them.

  3. 3

    Raster only if you must

    Raster pages renders each page to a JPEG at your chosen DPI and quality. It is effective and it is visible: fine type softens first, then edges. Judge it at 100 percent on the page with the smallest caption, not on a thumbnail.

Splitting is the last resort, not the first

If the form takes more than one attachment, Split PDF can extract ranges such as 1-6,9 into their own documents. Do it at the very end, from a numbered and verified master, so the parts carry consistent page numbers and you still hold one coherent document to work from when the requirements change.

What goes wrong

  • Compressing first and cutting pages afterwards, so the surviving pages are degraded for no reason.
  • Judging quality on the thumbnail grid, where everything looks fine.
  • Rasterising a portfolio that also carries a written statement, which loses the text a reviewer might search.
  • Maintaining four near-identical versions instead of one master you derive the parts from.
  • Screenshotting pages to shrink them, which adds a generation of loss and usually adds size as well.

The short version

  • Remove weak pages before compressing anything.
  • Resize the source images; the conversion embeds them as given.
  • Lossless cleanup rarely helps an image-heavy file, and its report tells you so.
  • Judge raster quality at 100 percent on the page with the smallest text.
  • Split last, from a verified master, only if the form accepts more than one file.

Measure what the file actually costs

Choose lossless cleanup or smaller raster pages with an explicit quality trade-off.

Was this article helpful?

Your answer stays in this browser. Nothing is sent to us. See how it works.

Keep reading

Reviewed and maintained by

Novus Stream Solutions Editorial Team

The Novus Stream Solutions Editorial Team maintains Novus PDF Studio's product documentation, tutorials and PDF explainers. The team checks product claims against the current browser-local implementation and tests, prefers primary specifications and vendor documentation, and corrects material errors openly. The byline identifies the responsible organization; it does not imply a named expert or professional adviser.

Privacy note: every tool mentioned in this article runs entirely in your browser. Nothing is uploaded or queued on a server. A PDF stays in the tab unless you explicitly use Save on this device, which stores that session in this browser without storing passwords. More on the how it works page.