Our Method
Direct answer: KBExact fits files by searching, not by slider: it binary-searches the highest quality that lands on your exact number, re-encodes a PDF's images before ever rasterising its pages, grows small files genuinely before resorting to disclosed padding, and publishes portal presets only from official sources with the date checked. And everything runs in your browser — by architecture, not by promise: there is no server for your file to go to.
Searching beats sliding
A quality slider makes you the search algorithm: drag, download, check, repeat. Our engine inverts it. You state the target; the engine tries the top quality, then bisects — higher if it fits, lower if it does not — until it holds the best quality whose output is inside your ceiling or window. Dimensions step down in measured 5% increments only when quality alone cannot reach the target. Every step happens locally; a batch of 20 images runs in a background worker so your phone stays responsive.
PDFs: re-encode first, rasterise last
A PDF is not a picture — it is a container of text, vectors and images. Most "PDF compressors" flatten the whole thing into page images, silently destroying selectable text and searchability. KBExact first rebuilds the PDF without its metadata and re-encodes only the embedded images, leaving text and vectors untouched. Rasterising happens only when the target cannot otherwise be reached, and the fixed disclosure appears in the report whenever it does: "This PDF was rebuilt as page images to reach the size — text is no longer selectable." You choose whether to download it or retry with a higher target.
Growing files: honest order of operations
Reaching a minimum is where tools quietly cheat with filler. Our chain is published and fixed: maximum-quality re-encode, then larger dimensions, then lossless saving — and only then, padding, always named in the report with the warning that some portals strip or reject padded files. If a genuine method can reach your floor, padding is never used.
Presets: official or nothing
Every preset on this site was read out of the portal's own notification or official requirements page; the source and the date we checked are printed with it. This rule has already changed what we ship: research for this site found SSC and RRB "photo sizes" quoted across the web that do not exist in the current official notices at all — both portals now capture the photograph live. So those pages explain live capture instead of selling you a resize you do not need. That is the entire brand: a number you can trust, or an honest "there is no number".
No uploads, by architecture
KBExact is a static site. The tools are code that your browser downloads once and runs locally; there is no upload endpoint, no account, and no analytics on your files. Verify it yourself in your browser's Network tab — we would rather you check than trust.
Questions
How can I be sure my file is not uploaded?
Open your browser's developer tools (Network tab), then run any tool. You will see no request carrying your file — the page and its code are downloaded once, and every byte of processing after that happens on your device. The architecture has no upload endpoint to send anything to.
Why do you show a "method" line in every result?
Because the honest differences between tools live there. A result reached by re-encoding is not the same object as one reached by rasterising or padding, even at the same byte count. You deserve to know which one you are submitting to a portal.
Where do preset numbers come from?
Only from official notifications and official portals, read by us, with the source and check date printed next to the preset. Where rivals contradict each other — and they do, often on their own pages — we publish nothing until the official document settles it.