Free image tools that never upload your files (and why that matters)

Why "free online" image tools aren't actually free

The cost of most free online image tools isn't money — it's your file. When you drag an image into a browser-based resizer or converter, the typical flow is: your image is uploaded to their server, processed there, then downloaded back to you. Processing happens on their infrastructure, which means your file transits their network and sits on their disk, even briefly.

For a random meme screenshot, this doesn't matter. For a client's unreleased product photo, a logo still under NDA, a financial document sent as an image, or a customer data export in CSV — it matters more than most people think about before clicking Upload.

The alternative is less inconvenient than it sounds. Modern browsers are fully capable of resizing, converting, and processing files without involving any server at all. If the tool is written to run entirely in the browser, your file never needs to leave your device — and you can verify that by disconnecting from the internet and checking whether the tool still works.

The system

Step 1: Understand the "client-side" test

"Client-side" means the code runs in your browser, using your CPU. The opposite — "server-side" — means your file travels to their machine and back. A genuinely client-side tool works with no internet connection.

The test is simple: disconnect from wifi, then try to use the tool. If it breaks, the processing is server-side. If it still works, it's genuinely local.

Toolbelt passes this test. Disconnect your machine and every image operation still works.

Step 2: Know which jobs need local tools

Some tasks are low-risk regardless:

• Checking an image's dimensions or format.
• Working with content you'd post publicly anyway.

Tasks where local processing matters:

• Client work — resizing or converting assets from a project that isn't public yet.
• Batch conversion of a source folder — you might not have looked closely at everything in the folder.
• Generating a favicon from a logo — you probably don't want your brand's first version of an unreleased mark going through a third-party server.
• Opening a CSV export — customer data, financial records, user lists, and internal reports are common formats here.

Step 3: Resize and convert images locally

Drag an image into Toolbelt's side panel — or right-click any image on a web page and choose "Send image to Toolbelt." Set the output dimensions with aspect-ratio lock or a preset, choose the output format (PNG, JPEG, WebP, or AVIF), set quality, and download.

For a batch, drag a folder in and export everything as a ZIP. The whole operation runs in the browser.

A practical note on formats: WebP and AVIF are worth defaulting to for anything going on a website. They're significantly smaller than PNG at the same visual quality — meaningful for page load speed (Core Web Vitals) and storage costs.

Step 4: Generate a complete favicon set without uploading your logo

Every project eventually needs a favicon. The typical path is either a web tool that processes your logo on their server, or an hour of manual resizing in an image editor.

Toolbelt's icon generator takes one source image and produces a folder-structured ZIP with:

• A multi-size favicon.ico (16×16, 32×32, 48×48)
• PWA web-app icons at the standard sizes
• Full iOS app icon ladder (every size Apple requires)
• Android launcher icon ladder
• Chrome extension icon sizes
• Social card sizes (Open Graph and Twitter)

That ZIP goes straight into your project. Nothing left your device to generate it.

Step 5: Open large CSV files without uploading them to Google Sheets

This isn't image work, but the principle is identical. A large CSV from a client — a customer export, a financial report, a user list — often freezes Excel and tempts you to upload it to Google Sheets. Google Sheets uploads the file to Google's servers. That's a reasonable trade for some files; it's a data-handling decision for others.

Toolbelt's CSV viewer uses a streaming parser and virtualized rows. Files that would crash a spreadsheet open quickly, and you can sort by column, filter, search globally, show or hide columns, and export a filtered view as CSV or JSON — all without the file leaving your machine.

Common mistakes

Assuming HTTPS means the file isn't stored. HTTPS encrypts the connection. It doesn't prevent the server from receiving and storing your file. A site can be HTTPS and still log every image you upload.

Not checking what a browser extension can actually access. An extension that requests "Read and change all your data on all websites" can read every page you open — not just its own panel. Toolbelt requests no host permissions at install. The only permission it asks for at runtime is loading an image from a live web page, and only if you drag one in.

Batch-converting a folder without looking at what's in it. Before dragging a folder into any tool, local or otherwise, check what you're processing. A folder synced from a shared client drive might contain files you're not supposed to move outside a specific environment.

Treating "offline mode" as a nice-to-have. If a tool works offline, it's genuinely not uploading anything — that's a stronger privacy guarantee than any privacy policy. It's worth asking the question before reaching for an online tool.

Related reading

• Toolbelt — full feature overview
• How to find and delete duplicate bookmarks in Chrome