How to compress a PDF to 200 KB for a job application

You have filled in eleven fields, uploaded a photo, retyped your address twice, and the last box on the form says Maximum file size: 200 KB. Your CV is 3.4 MB.

This happens constantly on government portals, university admissions systems and older corporate applicant-tracking software, and the limit is almost never explained. It is worth understanding why it exists, because the reason tells you exactly which lever to pull.

Why 200 KB, of all numbers

The cap is not about disk space. Storage has been effectively free for two decades. The limit is usually one of three things.

The first is an old upload pipeline that buffers the whole file in memory before writing it, sized for a load it was given in 2011. Nobody has touched it since, and raising the number means testing a component whose original author left the organisation.

The second is deliberate throughput management. A national exam board taking four hundred thousand applications in a fortnight has an entirely rational interest in every one of them being small. 200 KB × 400,000 is 80 GB; 3 MB × 400,000 is 1.2 TB, and now it is a budget conversation.

The third, and the most common in practice, is that the field is validated by a form builder with a default nobody changed.

None of those care what is in your PDF. They care about the byte count. That is good news, because the byte count is usually dominated by one thing.

What is actually making your file big

Open your CV and ask what is in it. Almost certainly: text, some formatting, maybe a photograph, maybe a logo. Text is astonishingly cheap. The full text of a two-page CV, stored as text, is around 4 KB — you could fit fifty CVs in the limit.

So the size is coming from somewhere else, and there are only a few candidates.

Embedded fonts. A PDF that embeds a full font family carries every glyph in it, including the Cyrillic, Greek and mathematical ranges you are not using. Four weights of a large font can be 600 KB on their own. Subsetting — keeping only the glyphs the document actually uses — usually cuts that by 90%, and most modern exporters do it automatically. Older ones do not.

Images at print resolution. A headshot pasted in at 3000 × 4000 pixels displays at two centimetres square and stores four thousand times more detail than it can show. This is the single biggest cause of a large CV.

A scan instead of a document. This is the big one. If you printed your CV, signed it and photographed it, you no longer have a text document — you have photographs of paper wrapped in a PDF container. A single phone photo of an A4 page at full resolution is 2 to 4 MB, and a three-page scan is 10 MB before anything else is added.

Everything the editor left behind. Revision history, embedded thumbnails, colour profiles, XMP metadata, forms and JavaScript. Individually small, collectively 50 to 200 KB.

Knowing which of these you have decides your approach entirely, so check first: try selecting a line of text with your cursor. If it highlights, you have a text PDF. If nothing happens, you have a scan.

If it is a text PDF

Start here, because the fix is usually free of any visible cost.

The first move is a lossless clean-up: subset the fonts, drop the metadata and the embedded thumbnails, and remove any objects nothing references. On a text-heavy document this alone routinely takes 800 KB to under 200 KB, and the output is pixel-identical to what you started with. Nothing has been degraded — you have only stopped shipping things nobody reads.

If images are still holding it up, downsample them rather than compressing harder. A photograph that will be looked at on a screen needs about 150 dpi; a logo that will be looked at politely and briefly needs less. Going from 600 dpi to 150 dpi removes 94% of the pixels and is invisible unless someone prints your CV and studies it with a loupe.

Only if both of those fail should you re-encode the images at a lower JPEG quality, and even then, stop before you reach the point where the artefacts show around text inside the image.

The PDF compressor does the clean-up pass first and only escalates if the target demands it, which is the right order.

If it is a scan

A scan is a different problem with a different arithmetic, and the honest answer is that the same techniques do less for you.

Photographs of paper compress badly because they are full of noise: paper texture, uneven lighting, the faint shadow of your own hand, JPEG artefacts from the phone camera. All of that is detail the encoder faithfully preserves, and none of it is information you want.

Three things help, in this order.

Drop the resolution to what a reader needs. 200 dpi is comfortably readable for 12-point text. 150 dpi is still legible. 300 dpi is what a scanner defaults to and is roughly four times the file size of 150 dpi for no gain on screen.

Convert to greyscale, or further. A signed document does not need colour. Greyscale removes two of three channels. If the page is genuinely black text on white paper, a bitonal conversion — every pixel either black or white — can be a tenth of the size again, though it destroys signatures and photographs, so check the result before sending it.

Straighten and crop. The margins around a photographed page are often 20% of the image, and they carry the desk, the shadow, and the edge of a laptop. Cropping to the page removes those pixels entirely.

With all three, a three-page phone scan can come down from 10 MB to 200 KB and stay readable. What it will not do is look good. Which brings us to the part most guides skip.

The trade-off nobody states plainly

There is a floor, and it is set by your content. A scan of three dense pages cannot reach 200 KB and remain comfortably legible — you can hit the number, but a human being will squint.

If you are near that floor, you have better options than compressing harder:

• Send fewer pages. Most application forms want the CV, not the CV plus three certificates. Extract just what is asked for.
• Rebuild it as a text document. If you have the original .docx, export a fresh PDF from it rather than scanning a printout. A two-page text CV exports at 80 to 150 KB with a photo in it.
• Re-photograph in better light. Even lighting produces dramatically smaller files than a shadowed page, because there is less noise for the encoder to preserve. This surprises people, and it is often worth more than any setting.

A compressed-to-death CV is a worse first impression than a slightly late application. Take the extra ten minutes.

Doing it without uploading your CV somewhere

A CV is a document with your full name, your phone number, your home address, your employment history and often your date of birth on it. It is, in identity-theft terms, close to a complete kit.

The standard advice is to run it through a free online compressor, which means uploading exactly that document to a company you have not heard of, in a jurisdiction you have not checked, whose retention policy you have not read. Most of them are fine. “Most” is doing a lot of work in that sentence, and there is no way for you to tell from the outside which ones are not.

There is no technical reason for the upload. Every step described above — parsing the PDF, re-encoding the images, subsetting the fonts, writing the file back out — runs perfectly well in a browser. The tools on this site do exactly that: the file is read by JavaScript in the tab, worked on by WebAssembly, and written back to your downloads folder. Nothing is transmitted. You can watch the Network tab in your browser’s developer tools while it happens, or switch off Wi-Fi and do it anyway.

The practical route

1. Check what you have. Try to select text. Text PDF or scan — the answer changes everything.
2. Clean up first. Run the compressor and let the lossless pass do its work.
3. If it is still too big, set a target. The 200 KB page takes the number and searches for the settings that land under it, instead of leaving you to guess at a quality slider and re-run it five times.
4. Check the result before you submit. Open it. Read a paragraph at 100%. Look at your signature. If anything is illegible, go back and remove pages instead of compressing harder.
5. Keep the original. The compressed copy is for the portal, not for you.

One last thing worth knowing: if the portal wants one file and you have several, combine them before compressing, not after. Merging first lets the compressor deduplicate the fonts across all of them, and shared fonts are frequently the largest single object in the result. Compressing three files separately and then merging them can produce a file noticeably larger than doing it the other way round.