Pre-set cap · 300 KB
JPG to PDF under 300 KB
Admission counters, court e-filing and document-update forms routinely reject anything past 300 KB. Here the whole document is measured — shell included — and every page is encoded just enough to land under the cap. The number on the result card is the number you will upload.
Drop images to build a PDF
or click to pick from your device. Each image becomes one page, in your order.
JPG · PNG · WebP · GIF one page per image stays on your device
The page order is the list order below. Photos with EXIF rotation are straightened automatically. With a cap on, every page is re-encoded just enough to fit under it — counted the way forms count, 1 KB = 1,000 bytes.
PDF is ready
The size on the result card is the exact size of the file you download.
How the 300 KB budget is shared
A 300 KB PDF holds 2–4 everyday document pages comfortably:
| Pages | Each page gets | Result |
|---|---|---|
| 2 | ≈ 150 KB | Comfortable |
| 3 | ≈ 100 KB | Comfortable |
| 4 | ≈ 75 KB | Comfortable |
| 6 | ≈ 50 KB | Readable — photos soften |
Why this cap will actually pass
Portals count 1 KB as 1,000 bytes; Windows File Explorer counts 1,024. A file at 300,000 bytes passes both readings — that is the guarantee this builder targets, and it measures the assembled document rather than estimating.
Need the pixels smaller instead of the bundle smaller? The resize tool trims dimensions; 100 KB and 50 KB preset pages compress the photos individually; the full PDF builder runs quality-first when no cap exists.
Three steps, one minute
- 01
Add your pages
Drop or paste photos of your documents — they stay on your device. Use the arrows to set the page order.
- 02
Aim at 300 KB
The cap arrives pre-set. Each page is encoded just enough for the whole PDF to fit under it.
- 03
Check the size, download
The result card shows the exact size of the file — and tells you honestly if it ever misses the cap.
300 KB, answered
Will the PDF really stay under 300 KB?
Yes — the finished file is measured, not estimated, and the page budgets are tuned over encoding quality and resolution until the total sits at or under 300,000 bytes. That passes whether the portal counts a KB as 1,000 bytes or Windows counts it as 1,024.
How sharp do the pages stay?
Text scans stay readable first — the encoder spends the byte budget wherever detail lives, and ink on white paper is the last thing to suffer. Photographs soften sooner; for very dense photo bundles the honest answer is fewer pages per PDF.
Can I photograph the pages instead of scanning?
Yes, and the budget still holds — but shoot square-on in daylight with the text filling the frame. Skewed or dim photos waste bytes on grain, and grain is exactly what a tight cap cannot afford.
My PDF came out over the cap — what now?
The result card says so plainly, with the exact overshoot: remove a page the portal does not require, or pick a bigger cap. The builder never claims a fit it did not get.
Do my documents get uploaded anywhere?
No. The pages are read, encoded and wrapped into a PDF entirely inside your browser — the same way an editor opens a file. Disconnect the internet after loading and it still works.
Different cap? See JPG to PDF under 200 KB, JPG to PDF under 1 MB.