PixelPress

Image tools that hit the exact number

A form says 100 KB. You need 100 KB — not 118 KB, not 74 KB. That single requirement is what these tools are built around.

  • No upload
  • Exact target size
  • Batch ready

Why “exactly” is the whole product

Most compressors answer a different question: they make a file smaller and show you a percentage. That is useless when the receiving system has a hard byte limit — you submit, get rejected, guess again. Here the target is an input, and the output is measured against it before you download.

Three things that are not negotiable here

  • Exact hit. The encoder searches quality, and falls back to reducing dimensions, until the file is under your number — never over.
  • No upload. Every tool runs in the tab. Open DevTools, drop a file, watch for a request: there is none.
  • Batch is native. Drop a folder, get 200 results with per-file status, retry and a client-built ZIP.

The sizes people actually search for

These are generated from the same registry as the tools, not hand-written pages — which is why every one of them does exactly what it says on the title.

How it works

1

Add images

Drop a file, several files, or a whole folder. Nothing is uploaded.

2

Set the spec

Pick the target from this page — it is already filled in for you.

3

Download

Exact-size output, or a ZIP when you came with a batch.

Frequently asked questions

Are my images uploaded to a server?
No. There is no upload endpoint in the processing path. Your browser decodes, re-encodes and hands you a download. You can verify it by cutting your network after the page loads — everything keeps working.
How exact is “exact”?
Within about 2% below your target and never above it. Getting byte-identical output is not possible with a lossy encoder, but staying under the hard limit is, and that is the requirement forms actually enforce.
Do I need an account?
No. No account, no email, no file history. The tools are free and there is nothing to sign up for.
What are the limits?
25 MB and 24 megapixels per file, 200 files per run. Those are browser memory limits, not business limits — a larger single file will crash a phone tab.