Image Studio
One private workspace for your images. Add multiple files once, then compress, resize, convert and clean them in a single pass — and download everything as a ZIP. Everything runs in your browser, so your images never leave your device.
Supported: JPG, PNG, WebP · Recommended ≤ 30 MB per file
Drag & drop images here, paste from clipboard, or
How it works
Image Studio processes files locally using your browser's canvas, off the main thread in a Web Worker where supported (with a main-thread fallback on older browsers). No image is uploaded to a server. The settings panel applies to every file in the list, so you choose a resize rule, an output format, a quality and an optional rename pattern once, press Process all, and each file is queued, decoded, redrawn and encoded in turn. The row for each image shows the before and after size, the saving as a percentage and the final pixel dimensions, and the thumbnail switches to the processed result so you can compare by eye before downloading.
What a single pass can do
- Resize by exact width, exact height, a percentage, or fit within a maximum width and height. Aspect ratio is always preserved, and an image that is already smaller than the target is left at its own size — the Studio never enlarges, because upscaling only adds blur.
- Convert to JPG, PNG or WebP, or keep each file's original format so a mixed batch stays mixed.
- Compress with a quality slider from 10% to 100% (80% by default). It applies to JPG and WebP output; PNG is lossless, so the slider is hidden when PNG is selected and ignored for PNG files kept as PNG.
- Flatten transparent images onto a background colour of your choice when the output is JPG.
- Rename outputs with a pattern built from
{name},{n},{n2}and{ext}:holiday-{n2}yieldsholiday-01.jpg,holiday-02.jpgand so on, in the order shown. The arrows on each row change that order. - Download each result on its own, or everything at once as a ZIP; if two outputs would share a name, the second gets a numeric suffix instead of overwriting the first.
A run can be cancelled part-way, and files that fail (a corrupted image, for example) are reported individually with a Retry failed button rather than stopping the batch.
Quick recipes
The recipe buttons fill in the settings panel; you can adjust anything afterwards.
| Recipe | Settings it applies | Typical result |
|---|---|---|
| Optimize for web | Fit within 1920 × 1920, WebP at 82% | A 12-megapixel photo of several MB usually lands at a few hundred KB |
| Shrink for email | Fit within 1280 × 1280, JPG at 72% | Small enough to attach a dozen photos to one message |
| Remove metadata before sharing | No resize, keep format, 92% | Same pixels, EXIF/GPS gone; size may change slightly |
| Convert to JPG (white background) | No resize, JPG at 85%, white matte | Transparent PNGs become opaque JPGs that open anywhere |
Supported formats
Input and output: JPG, PNG and WebP. HEIC and AVIF are not offered here — AVIF encoding is inconsistent between browsers, and HEIC needs a dedicated decoder — so we add them only once they work reliably across browsers, rather than claim support we can't deliver. iPhone HEIC photos can be converted first with the separate HEIC to JPG tool, which uses its own in-browser decoder, and then brought here. GIF files are not accepted as input. An animated WebP is read as its first frame only, so the output is a still image.
What happens to transparency and metadata
Converting a transparent PNG to JPG flattens it onto a background colour you choose (white by default), because JPG has no transparency. Re-encoding through the canvas removes EXIF/GPS and other metadata from the output. That applies to every file the Studio produces, whatever settings you use — there is no option to carry the original metadata across, and no copy of the original bytes is embedded in the result. If you only want the metadata gone and nothing else changed, the Remove metadata before sharing recipe keeps the format and dimensions, and the focused metadata tool does the same with a single button.
Limits
Processing happens on your device, so very large files or huge batches are limited by your available memory. The Studio warns — but still lets you continue — above roughly 30 MB per file, 150 MB per batch or 100 files, and tightens those thresholds on devices that report low memory. Images over about 100 megapixels are refused outright with a message, because a canvas that size can crash the tab. Work in groups of twenty or thirty photos on a phone; a desktop browser handles far more.
Worked example: a shoot for a product listing
Thirty JPGs from a camera at 6000 × 4000 and around 8 MB each — 240 MB in total, above the batch guideline, so split into two runs of fifteen. Set resize to fit within 2000 × 2000, output WebP, quality 80%, and rename to sku-4471-{n2}. Each image comes out at 2000 × 1333, typically a few hundred kilobytes, and the ZIP holds sku-4471-01.webp through sku-4471-15.webp ready to upload. Run the same settings on the second group with a different prefix, and the whole shoot is web-ready without an upload to anyone.
Troubleshooting
- An output is larger than the input.
- The row shows an orange “larger than original” flag. Lower the quality, choose a resize, or convert a photographic PNG to JPG or WebP; the Studio always gives you the file so you can decide.
- Quality slider has disappeared.
- Output is set to PNG, which is lossless. Switch to JPG or WebP if you want a quality trade-off.
- A file was rejected when added.
- Only JPG, PNG and WebP are accepted. Convert HEIC with the HEIC to JPG tool first; GIF and AVIF are not supported here.
- The browser became sluggish on a large batch.
- Cancel, clear the list and process in smaller groups. The memory warnings above the list tell you when a batch is over the recommended size.