About Resizo

17 tools that are free, need no account, add no watermark, and do their work on your own device instead of uploading your files. Here's what Resizo is, the limits it runs under, and who builds it.

The work happens on your device

Your browser’s own decoder opens most pictures. The encoder that writes the result, and the decoder a HEIC photo needs, are compiled to run inside a browser, and each is fetched from this site the first time a job needs it, not when the page opens. Your picture is read, changed and written back out by the machine you are sitting at. Nothing is uploaded, so there is no copy of your photo anywhere but on your own disk.

That also means there is nothing here to breach. No file store, no database, no account records — the deployment holds static pages and the image code, and it has no credentials for anything because there is nothing for it to reach.

There are no accounts

There is nothing to sign up for and nothing to log in to. Every tool works the same for everyone, with the same limits and the same output, and no step ever asks who you are.

Because nothing is kept, there is no history to look back on, no dashboard, and nothing tying what you processed to a name. The absence of an account is the feature: there is no record to keep, export or delete.

Limits, and why they exist

A single file is capped at 20 MB and 8,000 pixels on the longest side, with an output budget of 40 megapixels. A batch takes up to 20 files totalling 80 MB. There is no quota, no queue and nothing counting how often you use it.

These are not upsell gates. They are the size at which the job comfortably fits in the memory a browser tab is given. A photograph has to be unpacked into raw pixels to be worked on, and raw pixels are far bigger than the file: a 12-megapixel photo is about 46 MB of memory once opened, and an operation usually needs two of those at once.

So the honest limit is your own hardware, and it moves. A desktop with memory to spare will take a job an old phone will not. Every tool works the cost out before it starts and refuses a job that will not fit, with a sentence saying why and what to try instead — a smaller target, or resizing before compressing. That is deliberate: a tab that runs out of memory is closed by the operating system without warning, and on an iPhone it happens silently, so guessing and hoping would mean losing the photo you were working on.

This used to run on a server

For most of Resizo’s life the work happened elsewhere. Your file was sent to a server, a library called sharp did the resizing there, and the result came back in the reply. The argument for it was real: server hardware is predictable, one image library behaved the same for everyone, and a browser genuinely could not decode a HEIC or hit an exact kilobyte target.

That stopped being true. A browser will now run the same codecs compiled to WebAssembly, and for the common jobs it uses its own built-in image pipeline, which is quick. A job may first fetch the codec it needs from this site, but your picture never leaves your device. So the argument inverted. The old design asked you to hand a personal photo to a stranger’s computer for a job your own computer could do, and no promise about deleting a file afterwards is as good as never having it.

The trade is honest and worth stating. Results now depend on the device: a big photograph is slower on an old phone than it was on a server, and a job too large for the memory the browser can spare is refused instead of being sent away to succeed elsewhere. GIF went with the change and stays out — no browser exposes a GIF decoder to this engine, and an animation was never really a resizable still picture anyway. AVIF went the other way: the browser’s own decoder opens one directly, at no extra download, so Convert, Resize and the Bulk Image Converter all accept it as a source, on a browser recent enough to have it. Writing one is different. It needs an AVIF encoder, a separate download the page fetches from this site only when a job asks for an AVIF, and it is offered on Convert and for a single image on Resize; a batch writes JPEG, PNG or WebP. Refusing formats a browser genuinely cannot open is still the rule, it is just that AVIF crossed the line GIF has not. What you get back is a tool that works without a connection to us doing anything but serving the page, and a privacy claim that is a fact about the software rather than a policy about our conduct.

Who builds Resizo

Resizo is built and maintained by Sucheet Boppana. You do not have to take the no-upload promise on trust. The site’s security policy only lets a page talk to resizo.net itself, so your browser would block a page that tried to send your photo anywhere else. Your browser’s developer tools also have a Network tab that lists every request a page makes. Process a photo with it open and you will see requests that fetch the site’s own files, plus “blob:” entries, which are your photo and the result held in your browser’s own memory. None of them sends your photo anywhere.

Every core Resizo tool is free to use: no account, no watermark and no daily quota. There are no ads, no data brokered and no images retained to train anything.

The tools

  • Resize Image— Change image dimensions with pixel-perfect precision.
  • Compress Image— Reduce file size without visible quality loss.
  • Bulk Image Compressor— Compress many JPG, PNG and WebP files to a maximum size each, then download them one by one or as a ZIP.
  • Convert Format— Convert between JPEG, PNG, WebP and AVIF instantly.
  • Bulk Image Converter— Convert many JPEG, PNG, WebP and AVIF files to one format at once, then download them one by one or as a ZIP.
  • Crop Image— Remove unwanted areas with exact pixel control.
  • Favicon & App Icon Generator— Make favicon.ico, the PNG icons and an Apple touch icon from one logo in your browser — nothing is uploaded.
  • Convert HEIC— Convert iPhone HEIC photos to universal JPEG.
  • Signature Resizer— Crop, size and compress a scanned signature for an online form.
  • Passport & ID Photo— Crop and size a passport or ID photo to exact pixels, file size, format and DPI.
  • Image Size Fitter— Fit an image to exact pixels and a maximum file size in one step — crop or pad, encode, write DPI and check the file before download.
  • Passport Photo Print Sheet— Lay out as many copies of a passport or ID photo as fit on 4 × 6, 5 × 7, Letter or A4 paper at exact physical size, as a JPEG or PDF to print at 100 %.
  • Change Image DPI— Set the print resolution a JPEG or PNG claims, without re-encoding it.
  • Image Metadata Viewer— See the EXIF, GPS, XMP and colour-profile data stored in a photo without uploading it — the file is read in your browser and never changed.
  • Remove Image Metadata— Strip EXIF, GPS and XMP from a photo without touching its pixels.
  • JPG to PDF— Combine photos into one PDF, in the order you choose.
  • Merge PDF— Combine several PDFs into one file, in the order you choose.