Give your PDF an exact size target

The box wants a ceiling, not a wish

Tomas is applying for a research grant, and the submission form for his eleven-page proposal, novak-proposal.pdf at 2.8 MB, says one thing in small grey type: maximum file size 1 MB. There is no slider on earth that answers that sentence. A slider says medium; the form counts bytes. Only a number answers a number.

So the target box in the compress tool is a ceiling. Whatever you type, the engine treats it as the highest weight the finished file may have, and it hands you something lighter than that line. Type 1 MB and you get a file below 1,048,576 bytes. Type 300 KB and you get a file below 307,200 bytes. The result never sits exactly on the line, because landing on an exact byte count would need padding the file with filler, and this tool only ever takes weight away.

That one-way nature has a pleasant side effect. Load a file that already sits below your target and the tool tells you so instead of running: a 280 KB syllabus against a 500 KB target comes back unchanged, with a note that it was already small enough. Compression you do not need is compression you do not get.

KB, MB, and the two ways to count them

Here a kilobyte is 1,024 bytes and a megabyte is 1,024 kilobytes, so a 1 MB target draws its line at 1,048,576 bytes. The unit switch beside the box does the arithmetic for you: type 1 with MB selected and the engine aims under that count. Typing 1024 with KB selected aims at the same place.

Trouble starts because not everybody counts this way. Some upload forms reckon a kilobyte as a flat 1,000 bytes, which makes their ceiling sit about 2% lower than the same number here at KB sizes, and about 5% lower at MB sizes. The symptom is unmistakable: your file reads as fitting, yet the form rejects it anyway.

The fix is a margin, not a fight. When the form says 100 KB, type 97. When it says 1 MB, type 975 KB instead. The extra shave is invisible on the page, and it absorbs the difference between the two ways of counting. After a rejection, always trust the size the receiving system reports back over the size your own file manager shows: the receiving counter is the one that decides.

Run it with a number

1. Open the compress tool and drop your PDF onto the page.
2. Read the cap on the receiving form, word for word, including the unit.
3. Type that number into the target box, pick KB or MB to match, and shave a few percent off when the form has rejected a fitting file before.
4. Press Compress, compare the finished size with the cap, and download when it fits.

In a hurry with no stated cap at all? Leave the target box empty. The tool then falls back to 500 KB, or to just under your file size when the file itself is lighter than that, and works toward the fallback as if you had typed it.

Before you press Compress

A thirty-second review catches nearly every failed run. Walk this list first.

• The number in the box is the recipient's ceiling, not your file's current size.
• The unit matches the form: KB with KB, MB with MB, converting 1 MB to 1,024 KB when they differ.
• A rejected-before form gets a target a few percent under its stated cap.
• The loaded file is the right one: check the name shown beside the drop zone.
• The file opens without a password, since an encrypted file resists compression until it is unlocked.
• You know the plan if the result lands above the line: fewer pages, split parts, or a second run with a lower ceiling.

Mistakes that cost you a second upload

Typing a bigger number than the file. Asking for 2 MB from a 900 KB document cannot change anything, so the box flags the target while you type and clamps it to just under the loaded file when the run starts. Read the flag as a hint: the file already fits, send it as it is.

Demanding an exact byte count. Nobody can promise a file of precisely 204,800 bytes without stuffing it with invisible filler, and no honest tool does that. Aim under the cap with a small margin and stop chasing the exact integer.

Confusing MB with Mb. An internet plan measured in megabits has nothing to do with a file measured in megabytes. When a form writes MB, it means megabytes: 1 MB here is 1,048,576 bytes.

Rounding the cap upward. A 2.4 MB cap is not a 3 MB target. Rounding up throws away nothing, but rounding down to 2 MB keeps a margin for the counting difference; round toward safety, never toward comfort.

Recompressing an already squeezed file. Running the downloaded file through the tool again at the same target changes nothing except your afternoon. Each pass removes the easy weight first, so the second run at the same ceiling has nothing left to take.

When a smaller number is not the answer

Sometimes the number points the other way. A form that demands a minimum file size, rare but real in print and archive uploads, cannot be satisfied by any compression tool: nothing here pads a file upward. The honest fix is better source material, usually a fresh scan at higher resolution or an export with full-size images, not a bigger number in a shrink box.

Sometimes the file is not yours to shrink. A statement downloaded from a bank portal that refuses to compress is often encrypted, and the password prompt in your viewer is the giveaway. Unlock your own copy first, then set the target.

And sometimes the cap itself is negotiable. A landlord asking for documents by email will usually accept two messages or a shared folder link when one attachment will not fit. The email guide covers splitting and link-sending for exactly that case, and the general shrinking walkthrough explains what inside the file decides whether a target is reachable at all.