Pixel Target — Exact Image Size & Format

Hit an exact image file size right inside any upload form — no compressor round trips. 100% on-device, nothing is uploaded.

A portal wants a photo under 20 KB. You leave the form, open a compressor, come back with 21 KB. Rejected. Try again: 14 KB, and now it is blurry. Try again for the right format. Try again because the file is named `photo (1).JPEG`. Pixel Target removes every one of those round trips. It works inside the page you are already on: it reads the size rule off the form, encodes your image to land **at or under** that number on the first attempt, and drops the finished file straight back into the upload field. No other tab, no Downloads folder, no re-picking. **What it does** - **Exact targets, never over.** Ask for 20 KB and get 20 KB or just under. The search only ever keeps candidates it has already measured under budget, so the result cannot come back at 21 KB. - **Minimum sizes too.** Portals that demand *at least* 20 KB are handled by padding the file with format-legal filler bytes — a 14 KB photo becomes exactly 20 KB without re-encoding a single pixel or blurring it further. - **Format conversion.** JPEG, WebP and PNG, filename extension included, since plenty of servers validate the extension string rather than the MIME type. - **Reads the rule off the page.** "Photo must be less than 200 KB" in the form's own help text is picked up automatically, so usually there is nothing to type. It reads strictly — one sentence, near the field, only when it plainly states a believable file size — because inventing a limit is worse than missing one. - **Fixes it without being asked.** When the page states a rule your image breaks, the file is resized and put back into the form immediately, with a chip saying what happened and an undo. Prefer to be asked first? Switch it off in the popup. - **Learns from a rejection.** Many portals print their real limit only when they turn a file away. Pixel Target reads that complaint, applies it to the file still in hand, and remembers it for that field — so there is no second attempt, and later uploads need no detection at all. - **A slider to nudge it.** Logarithmic, because upload limits run from a 20 KB signature to a 5 MB scan. Every drag re-encodes and shows the new size. - **Swaps the file in place.** Into ordinary file inputs, into drag-and-drop zones that never use a file input, and into pasted screenshots. - **Standalone mode.** The toolbar popup converts images that are not attached to a form yet. **Details that portals actually care about** - **Keeps the picture worth looking at.** A 1600×1200 photo *can* be squeezed into 20 KB at full resolution, but only at a quality where it comes out blocky. When that happens the search trades resolution for quality instead — on a real encoder, a full-size quality-0.05 mess becomes a clean 597×448 at quality 0.43, for the same 19.6 KB. - **Pixel floors are respected.** If a form also states minimum dimensions, the search stops and reports the byte target as unreachable rather than shrinking past the other rule. - **DPI.** Canvas always writes 72; portals asking for "200 DPI" read the JFIF density field, so it is stamped after encoding. - **Sharpening.** Downscaling softens an image and blur checks reject soft photos, so an unsharp mask runs before the quality search — the restored detail counts against the byte budget. - **Filenames.** Spaces, accents and extra dots are reduced, and JPEG always leaves as `.jpg`. Portals reject all of these and blame "invalid format". **Privacy — everything stays on your machine** Images are decoded, resized and re-encoded entirely inside your browser using its own canvas. The extension makes **no network requests of any kind**. Your image bytes are never uploaded and never leave your device. Stored locally: your settings, the size rules learned from sites you upload to (address and limits only), and a count of images processed. Learned rules can be erased any time from the popup under **More → Learned sizes → Forget all**. **Known limits** - HEIC/HEIF cannot be opened — Chrome ships no decoder, and the panel says so rather than failing quietly. - Some uploaders read the file the instant you pick it and ignore a later swap; when the swap is refused, Download is offered instead. - Photos captured by a page's own webcam never pass through a file input, a drop or the clipboard, so nothing can reach them. - Pasting into a text editor is left alone. - Animated GIF/WebP are flattened to their first frame. - Padding to a size floor appends filler bytes; a server that re-encodes and re-checks will see the re-encoded size, not the padded one. Chrome 109 or newer. ## Permission justifications - **storage** — saves your settings and the size rules learned from sites you upload to. Nothing is ever transmitted. - **Host access (content script on all pages)** — upload forms exist on any site, so the script must run wherever one appears. It reads only the text near an upload field and the files you choose, in order to detect the stated size limit and place the resized file back into the form. It sends nothing anywhere.