The 500 KB budget is already armed. Drop your pages and they come back as one PDF at or under the number, its size printed beside the cap. Built for visa document sets and packets of five to ten pages. Part of image to PDF and the image converter.
– / –
Drop images or browse
JPEG · PNG · WEBP · AVIF · HEIC · up to 50 at once · max 30 MB each
HEIC
PNG
JPEG
AVIF
WEBP
Advanced settings1 on
SmallerAutoBetter
Chosen automatically to hit your size cap.
Split across the pages you drop, the file’s own overhead set aside.
Max resolution
×
Empty side keeps the ratio. Never enlarges.
Every format and budget, one PDF
The same converter under the name your file has, or with the size your form demands already armed. Under it, or a clear error, and never over.
The engine behind every page, on a real photograph: 9.8 MB in, 97.1 KB out. Each page of your PDF goes through the same engine, as a JPEG, with its share of the 500 KB budget as the hard ceiling.
How the 500 KB budget is split across the pages
The budget covers the whole file, so the split happens at drop time, before any upload. The wrapper’s share is set aside first: 1 KB plus 0.5 KB a page, an upper bound on what the assembler writes around the pages, pinned by a worker test against real files. The rest is divided by the page count, and each page is capped by the engine’s hard cap at its share, which it never overshoots. One page under 500 KB gets 498.5 KB; three get 165.8 KB each; five get 99.3 KB each. A share under the 10 KB floor is refused in words before anything uploads, which under 500 KB happens at 48 pages: “500 KB across 48 pages leaves 9 KB a page; the floor is 10 KB. Drop fewer pages or raise the cap.”
Pages
Relative to source
Set aside for the wrapper
Each page's cap
1 page
1.5 KB
498.5 KB
3 pages
2.5 KB
165.8 KB
5 pages
3.5 KB
99.3 KB
10 pages
6 KB
49.4 KB
The split for 500 KB (500,000 bytes), computed by the same shared code the tool runs at drop time. The wrapper column is the bound set aside, not the bytes the file finally spends on it.
JPG to PDF under 500 KB: the reference photo as 1, 3 and 5 pages, measured
Pages
Each page's cap
PDF
Note
1 page
498.5 KB
496 KB
each page quality-searched to its share
3 pages
165.8 KB
486 KB
each page quality-searched to its share
5 pages
99.3 KB
488 KB
each page quality-searched to its share
Source: photo.jpg, 576.8 KB at 1920×1280, dropped as 1, 3 and 5 pages under 500 KB, split by the code above and assembled by the same code that builds your file. Sizes in 1,000-byte kilobytes, the unit the cap is stated in.
Every byte count is the size of the actual file our engine produced from the named source, the same bytes you would download, not an estimate. The reference photo is one of our own photographs, an iguana on a branch, and the camera photo is a real one too. Drop your own file into the tool above to rerun any of them. How we measure names the sources and the settings.
JPG to PDF 500 KB: the same page, with or without the word "under"
Forms ask for it both ways. JPG to PDF 500 KB and JPG to PDF under 500 KB describe one job: images in, one PDF out, at or under 500 KB. Indian portals usually write the number alone, so that is the phrasing you will have seen on the form. The budget above is already armed at 500 KB; the result prints its real size beside the cap, and it is never over. Photos, screenshots and iPhone HEIC all go in; what comes out is a PDF an upload validator accepts.
The 500 KB jobs: a whole packet, one document per PDF
Five hundred kilobytes is the packet number. Five pages under this cap get 99.3 KB each, seven get 70.8 KB each and ten get 49.4 KB each. Our 576.8 KB reference photo as five pages assembled to 488 KB. Without a cap, a page of the same photo at auto quality weighs 273.9 KB, so one page at auto quality fits under 500 KB. The cap earns its keep from 2 pages, or with camera-resolution photos like the 9.8 MB original on the home page. The sourced spec is India's regular online visa application: every uploaded document is "Format PDF", "Size Minimum 10 KB", "Maximum 500 KB", and "the application is liable to be rejected if the uploaded document is not clear and as per specification". Read that as a recipe: one document per PDF, every page upright, the desk cropped away, and the file inside the window. Drop order is page order, so select the pages in the order the document reads. A blank back page is bytes for nothing; leave it out.
Inside the window: the portals that set a floor as well as a ceiling
Three of the portals behind this family reject a PDF for being too small: the NTA’s NEET (UG) 2026 bulletin sets a 50 kb floor under its 300 kb certificate ceiling, UPSC’s one-time registration FAQ a 20 KB floor under 300 KB for the photo ID, and India’s e-Visa portal a 10 KB floor under 300 KB for the passport page. So the job is a file inside a window, not the smallest file possible. The cap here searches for the most quality at or under the number, never for the fewest bytes. A page already under its share and carrying no metadata comes back as it was. Our 576.8 KB reference photo is over a one-page share of 500 KB, so the engine lowered its quality: the PDF landed at 496 KB, close under the cap rather than as small as it could go. After the run the card prints the assembled size beside your cap, so you can read it against the floor before you upload. On this page 500 KB is the ceiling; your notice names the floor.
When 500 KB is the wrong tool
A PDF you already have?
This tool builds PDFs from images only. It does not shrink, split or merge an existing PDF file.
The pages cannot share 500 KB?
A share under the 10 KB floor is refused. Drop fewer pages, raise the cap, or make two files and upload them to two fields.
Text that must stay selectable?
Pages are pictures, not OCR. A scanned contract stays a picture of a contract.
No rule demands a size?
Use the plain image-to-PDF page with Auto quality. It lands light without betting quality on a number.
The budget is already armed above. One drop settles most of these.
Q:How do I convert a JPG to PDF under 500 KB?
Drop your images. The 500 KB budget is already armed in the Max PDF size field. At drop time it is split across the pages: the wrapper set aside, the rest divided by the page count, each page capped by the engine's hard cap at its share. One page gets 498.5 KB; three get 165.8 KB each. The pages compress, combine into one A4 PDF, and the card prints the size beside your cap.
Q:What happens if 500 KB is too small for the pages I drop?
The drop is refused in words before anything uploads. Each page's share must reach the engine's 10 KB floor, and under 500 KB it falls short at 48 pages: "500 KB across 48 pages leaves 9 KB a page; the floor is 10 KB. Drop fewer pages or raise the cap." Two files is the other way out. A page that runs but cannot make its share is left out and the card says so; the file is never over.
Q:Is 500 KB counted in 1,000-byte or 1,024-byte kilobytes?
In 1,000-byte kilobytes: we count 1 KB as 1,000 bytes and 1 MB as 1,000,000 bytes, so 500 KB here is 500,000 bytes, the way the size field counts. A portal that measures in 1,024-byte units allows slightly more, so a file that meets our number passes both readings. That matters most on a tight cap, where a few hundred bytes decide the upload. The card prints the assembled size after the run.
Q:Why is part of the 500 KB budget set aside for the wrapper?
Because a PDF weighs its pages plus the structure around them: the catalog, the page objects, the image dictionaries. Measured, that wrapper is 1.8 KB on our three-page file and 2.6 KB on five. The split sets aside a little more, 1 KB plus 0.5 KB a page, an upper bound a worker test pins against real files. So the pages can use their whole share and the total still lands under the number.
Q:Can I combine several JPGs into one PDF under 500 KB, in order?
Yes: up to 50 JPGs in one drop become one PDF, one page per image, in the order you dropped them. PNG, WebP, AVIF and iPhone HEIC can join them. Under a budget every page is embedded as a JPEG, PNG included, because only a JPEG stream goes in byte for byte and keeps the cap a promise. Those are conversions: up to 10 a run. Sideways photos straighten from their orientation tag first.
Q:Is it safe to put ID scans, certificates and signatures in a 500 KB PDF here?
Yes. We strip EXIF and GPS from every page we embed, so a photographed document stops carrying where it was shot. We process files and wipe them automatically: we keep nothing, never archive, never reuse. You need no account, so no profile collects your uploads, and there is no watermark and no sign-in wall before the download. The privacy policy carries the detail.
Q:Should I make one 500 KB PDF of every page, or one PDF per document?
Whatever the form's fields say. A field per document wants one PDF each, and a one-page file then gets 498.5 KB to itself. One field for a packet wants one file, with 500 KB split across its pages. Portals that list documents separately, the NTA's NEET bulletin among them, expect each in its own field. When in doubt, one document per PDF: it is sharper and easier to replace.
Q:Does the PDF ever come out over 500 KB?
No. Each page is capped by the engine's hard cap at its share, and the engine never overshoots a cap: it searches quality, then dimensions, and fails a page rather than exceed the number. The wrapper is bounded above. So the assembled file is at or under 500 KB by construction, and the card prints the size the server measured beside your cap, so you see it rather than take our word.
Q:How many pages can a 500 KB PDF hold?
Up to 47 pages before a share drops under the 10 KB floor, and far fewer if you want to read them all. Ten pages get 49.4 KB each and twenty get 24.4 KB each. Our 576.8 KB reference photo as five pages assembled to 488 KB with 99.3 KB a page. Past ten pages a photo page softens; two files of ten is the better answer than one soft file.
Q:Do I need to compress my photos before converting?
No. Each page runs through the compression engine on the way in, capped at its share of the 500 KB budget, so there is no second tool and no retry loop. Drop the camera originals as they are; iPhone HEIC needs no JPG detour. A JPEG already under its share and carrying no metadata comes back untouched; anything else gets one capped re-encode. The card prints the assembled bytes.
Q:How do I keep the page order when converting many images?
Drop order is page order. Select the files in the order the document reads and the PDF follows it; there is no drag-to-reorder step afterwards, so a wrong order means a second drop. Sideways photos straighten from their orientation tag before they are embedded. For a deliberate turn, rotate the picture first with the rotate tool, then drop it into the batch with the rest.
