The short version

250 KB here means 250,000 bytes, which is the figure most upload validators actually check. The tool works down to it in three stages, stopping at the first that fits.

The result line reports the exact byte count rather than a rounded one, because at this size a few kilobytes is often the whole margin.

Most single-page documents clear 250 KB without much argument. A page of text costs about forty kilobytes, a greyscale scan about a hundred and thirty, and a colour scan close to a quarter of a megabyte on its own. So the interesting question at this size is rarely whether the file can be made to fit. It is whether the number you are aiming at is the number the portal is checking.

Where the 250 KB limit comes from

Who asks for itPlaces that cap uploads at 250 KB
  • State recruitment and exam portals250 KB per document
  • Bank and insurance KYC uploads250 KB per page
  • Visa appointment document slots250 KB to 1 MB
  • University admission portals250 KB per certificate
  • Scholarship and grant applications250 KB per attachment

The number itself is arbitrary. It is a quarter of a megabyte, which is what you get when somebody budgets one megabyte for a set of four documents and divides. That origin is worth knowing, because it tells you the cap is a share of a total rather than a considered judgement about legibility, and totals are often more flexible than the per-file number suggests.

How the tool hits 250 KB

1

Add the PDF

This tool aims at 250,000 bytes rather than 256,000, because a portal that says 250 KB usually means the decimal number. The file is read into memory and measured against that figure.

2

The free stage, then the ladder

Structure is cleared first for nothing. The images then step down, and at a quarter of a megabyte a two-page greyscale scan usually settles in the middle rungs with its text untouched.

3

Stage three, and the margin that avoids it

The gap between 250,000 and 262,144 bytes is small, but it is often precisely what keeps a file out of a rebuild. When a rebuild is needed the pages become images with a searchable layer behind them.

4

Download, and read the result line

It gives the byte count rather than a rounded figure, so you can see whether the file cleared the number the portal actually checks.

The image ladderSeven rungs, from 200 ppi down to 60
200q82150q75120q66100q5880q5072q4260q36Rung 1: images barely touched (ppi above, JPEG quality below)Rung 7: visibly softYour text, links and form fields are untouched at every rung
Stage two walks down this ladder, recompressing the pictures inside the file and leaving everything else alone. It stops at the first rung under 300 KB, and abandons the ladder early when the images are not what is making the file big.
Stages
Three

Structure, then the images in place, then the pages as pictures. It stops at the first stage that fits.

Text after compression
Kept

Untouched at the first two stages. If the pages do get rebuilt, an invisible text layer keeps them searchable.

Bytes uploaded
0

The IDs, forms and statements people compress for portals never leave the device.

What fits in 250 KB, and what does not

Text pages are cheap because a rendered page of black type compresses extremely well. Colour scans are expensive because every pixel carries information the encoder has to keep. At 250 KB a single colour page is the whole budget, and a second page has to come out of it.

Try it

Will your file fit in 250 KB?

Enter the page count and what the pages contain. The estimate shows the attempt that is likely to succeed and what that attempt looks like.

Typical sizesCommon documents against the 250 KB line
2-page text documentabout 100 KB1-page colour ID scanabout 250 KB3-page greyscale scanabout 400 KB2-page colour scanabout 490 KB250 KB
Estimates before any quality is traded away. The two over the line have to go down the image ladder, and a colour pair usually needs the pages rebuilt as pictures.

When it cannot reach 250 KB

A file that lands just over 250 KB is often a rounding problem rather than a quality problem. Check in this order:

  • Confirm which 250 the portal means. This tool targets 250,000 bytes. If the portal actually allows 256,000, a file that missed here by a few kilobytes will upload without any further loss.
  • Check what your operating system is reporting. Windows and macOS disagree about what a kilobyte is, so the same file can read as 244 KB in one place and 250 KB in another. The byte count is the only figure that settles it.
  • Split if it is genuinely too large. Where the file really is over, Split PDF and compress the parts, which most portals accept.
Bytes, not kilobytes
Upload validators almost always count bytes, so that is the number worth watching. The result line above gives it exactly rather than rounding, which is the point of showing it.

250 KB, or 256,000 bytes?

A kilobyte is a thousand bytes when a disk manufacturer says it and 1,024 bytes when a programmer says it. Both readings are alive inside the same upload forms. A check written as size > 250 * 1024 refuses anything over 256,000 bytes. One written as size > 250000 refuses anything over 250,000. Between them sits a band of exactly 6,000 bytes where a file passes one portal and fails the next while looking identical in both.

The disputed bandWhere the same file is accepted and refused
accepted by both readingsin disputerefused by both250,000decimal reading256,000binary reading6,000 bytesfile size in bytes
Drawn to scale. A file in the amber band clears a portal that reads the cap as 256,000 bytes and is refused by one that reads it as 250,000. Nothing on screen distinguishes the two.

Six thousand bytes sounds like nothing, and most of the time it is. It matters here because a 250 KB cap is usually applied to a single scanned page, which is the one case where the finished file and the ceiling are the same order of magnitude. When a document has to shed ninety per cent of its weight, six thousand bytes is noise. When it only has to shed five, that is most of the margin.

So this page targets 250,000 bytes, the smaller of the two readings. A file that clears it clears both, and the price is about two per cent of the budget, which is not something you can see on a page. The other pages in this set aim at the decimal reading too, for the same reason: a file under it clears a validator that counts either way. Where the distinction could matter to you, the byte count is the thing to check, not the kilobyte figure your file manager displays.

If you are looking at a rejection you cannot explain, check this before anything else. Open the file's properties and read the size in bytes rather than in kilobytes. Windows divides by 1,024 and macOS divides by 1,000, so a file of 253,900 bytes displays as 247 KB on one machine and 254 KB on the other. Neither figure tells you which side of the portal's line it falls on. The byte count does.

Where people use the 250 KB target

Typical jobsWhat gets compressed to this size
  • Exam and recruitment form attachments1 page, fits in colour
  • KYC document sets1 page each, fits
  • Admission certificates and mark sheets1 to 2 pages, greyscale
  • Visa supporting documents1 page, borderline in colour

Why this runs in your browser

The documents that get compressed to 250 KB are identity documents: passports, national ID cards, degree certificates, bank letters. Uploading one to a compression website so that you can upload it again to the portal doubles the exposure and buys nothing.

Two ways to compressOne of them never transmits the document
Your devicePDFin memoryBrowser enginecompressDownload0 bytes leavethe machineTypical online toolPDFon diskuploadServercopies filedownloadA full copy now sits on hardware you do notcontrol, under a policy you cannot audit
PDF.js renders the pages and pdf-lib rebuilds the file inside the tab. The document is read into memory, compressed there, and offered as a download.

The tool is right above

Everything on this page runs in your browser. Scroll up, drop the file, and keep it on your machine.

Jump to the tool

Common questions

Questions that come up around a 250 KB limit.

01Why does this tool aim at 250,000 bytes rather than 256,000?

Because a 250 KB cap is read two ways and a file under 250,000 bytes clears both. The few kilobytes it costs are invisible; a rejection is not.

02What fits in 250 KB?

A one-page colour ID scan uses close to the whole budget. Two or three pages of text fit easily. Two colour pages need the image ladder.

03My file shows a different size on Windows and Mac. Which is right?

Both. Windows divides bytes by 1,024 and macOS divides by 1,000, so the same file reads 247 KB and 254 KB. Compare the byte count with the portal's limit instead.

04My file is already under 250 KB. Do I need this?

No. The tool checks first and hands a file that already fits straight back untouched.

05Colour or greyscale at this size?

Greyscale unless the colour is evidence. At 250 KB a greyscale page buys noticeably more resolution than a colour one, and resolution is what makes small print readable.

06Will the text still be selectable?

Usually. The first two stages leave text exactly as it was. If the pages have to be rebuilt as pictures, an invisible text layer goes behind them so the words stay searchable.

07Are my files uploaded anywhere?

No. Rendering and compression run in your browser. The file never leaves the device.

08Is it free?

Free. Every tool, unlimited use, no signup.