Images are usually the heaviest thing on a web page. A 3MB hero photo will tank your Core Web Vitals faster than almost any other mistake, and a single EXIF leak in a screenshot can dox a beta tester. Most teams reach for Photoshop, a CLI tool, or a paid SaaS to fix these problems. You don't need any of that.
These five browser-native image tools handle the 90% of image work that actually comes up in a normal week. Everything runs locally — your files never leave your machine — and nothing requires an account.
Why Browser-Native Image Tools Win
The default image workflow is broken. You upload a 4MB photo to a cloud compressor, wait 30 seconds for a download link, hope the service doesn't add a watermark, and discover the result lost quality. Repeat for the next 30 images.
Browser-native tools flip the script. The file is read with the File API, processed in a Web Worker, and downloaded — no round trip, no quota, no privacy concern. On a modern laptop the Image Compressor can crunch a 5MB JPEG down to 800KB in under two seconds.
The other win is composability. You can chain tools in a single session: strip metadata, compress, resize, convert to WebP, and ship. No context switching, no export-import-export dance.
The Five Tools
1. Image Compressor — Your Default First Step
Every image that lands on a server should pass through compression first. The Image Compressor lets you drop a batch of JPEGs, PNGs, or WebPs and tune a target quality slider. It re-encodes locally using canvas, so what you see is exactly what gets saved.
The practical use case: a marketing team emails you twelve 4MB product photos. You drag the folder in, slide quality to 80, and 90 seconds later you have twelve files averaging 600KB. The visual difference is invisible on a Retina display, and the page weight just dropped by 85%.
The smart defaults matter too. It preserves EXIF orientation, falls back gracefully on unsupported formats, and lets you compare before/after side by side so you're not guessing.
2. Image Metadata Viewer — Stop Leaking EXIF
EXIF data is a quiet privacy hole. The default iPhone photo carries GPS coordinates, the device serial, the exact timestamp, and often a thumbnail of an unrelated shot from earlier that day. Upload a screenshot of a Stripe dashboard to a public bug tracker and you've leaked your account email.
The Image Metadata Viewer reads the full EXIF block locally and shows you what's actually in the file. If anything looks sensitive — and it almost always does — it generates a stripped, privacy-safe copy in one click. No upload, no third-party server, no log of your activity.
For a content team, this is the difference between publishing a product photo and publishing a product photo plus a Google Maps pin to your office.
3. Batch Image Resizer — Bulk-Ready Dimensions
Compression shrinks bytes; resizing shrinks pixels. Both matter, and most teams skip the second step because doing it in Photoshop means opening 40 files one at a time.
The Batch Image Resizer takes an entire folder and a max width/height, and emits a parallel set of files in the same names. The "fit within" mode preserves aspect ratio, the "cover" mode crops to exact dimensions, and the output is deterministic — running it twice on the same input produces the same output, which is the only way this kind of tool belongs in a build pipeline.
The actual use case: a CMS migration. You have 200 product images at 3000×2000, and the new theme renders them at 800×533. Batch resize to 1600 (2x for Retina) and you've cut total image payload from 1.2GB to 140MB without touching a single line of theme code.
4. Placeholder Image Generator — Stop Mocking With Real Photos
Hard-coding https://picsum.photos/800/600 in a component is a rookie move. The image will eventually 404, the seed will collide with a real customer's photo, and the network call will wreck your Lighthouse score during the demo.
The Placeholder Image generator lets you dial in exact dimensions, a hex color, a format (PNG, JPEG, WebP), and even text. Drop the generated data URI straight into your markup and there's no network call at all.
Use it for: storybook fixtures, Storybook docs, marketing landing pages in staging, and any Lorem-Ipsum-style image slot that isn't supposed to be a real photo. It also produces properly-sized placeholders for responsive srcset testing, which is the kind of thing that always takes longer than expected.
5. Base64 to Image Decoder — Reverse the Embed
You'll encounter base64 image strings in three places: data URIs in legacy HTML, API responses that returned an avatar inline, and copy-pasted chat messages from a designer. Converting them back to a real file is annoying, and most image editors refuse to open a 2MB string of random characters.
The Base64 to Image Decoder takes the raw string, decodes it, previews the result, and offers a download with the correct extension inferred from the MIME header. Paste a data:image/png;base64,iVBORw0KGgo... blob, get a photo.png you can actually open.
It's also handy for debugging. If a CSP rule is blocking an image and the error console just says "refused to load," the fix is often to inline the asset as base64 and skip the network layer entirely.
Workflow: A Real Image Pipeline in Your Browser
Here's the actual sequence I run on a new feature drop:
1. Designer hands over a zip of 30 PNGs from Figma export. Most are 3-5MB.
2. Drop them into the Batch Image Resizer at 2x target dimensions. Wait 20 seconds.
3. Run the output through the Image Compressor at quality 82. Wait 15 seconds.
4. Spot-check three random files in the Image Metadata Viewer. Strip any GPS or device data.
5. Zip the result and ship to the CMS.
Total wall time: under a minute. Total cost: zero. Files touched a network: only the final CMS upload.
FAQ
Are these tools actually free, or is there a tier?
Completely free. No signup, no quota, no "premium" tier hiding the good features. Everything on TinyToolbox runs in your browser, which is also why there's nothing to bill you for.
Do my images get uploaded to a server?
No. All five tools process files locally in the browser using the File API and Canvas. You can verify this by opening DevTools, going offline, and reloading the page — the tools still work.
Can I use these in a CI/CD pipeline?
Not directly, since they're browser-based. For build-time image optimization, the equivalent open-source CLI tools are Sharp (Node) or ImageMagick. These browser tools are for the human-in-the-loop passes — design reviews, content uploads, one-off fixes.
Wrap-Up
Image work doesn't need Photoshop, a paid SaaS, or a 200MB CLI install. The five tools above cover compression, metadata, bulk resizing, placeholders, and base64 decoding — which is roughly 95% of what a web developer actually does with images. Bookmark the Image Compressor first, since it's the one you'll reach for daily. The rest earn their place in the tab bar over the next month.