About

Nutter Tools is a toolbox, not a service.

Nutter Tools (nutter/tools) converts, compresses, and resizes files entirely inside your browser. The codecs are compiled to WebAssembly and run on your device. When you drop a file on one of these pages, it is processed locally and never uploaded. I could not read your files even if I wanted to: they never reach a server I operate.

I build and maintain it on my own. No company, no team, no support queue.

Where the name comes from

The name is a reference. In Vice City, NUTTERTOOLS was the cheat code I typed as a kid to get the heavy weapons. I liked that feeling: a pile of tools, ready for whatever I was about to do.

This site is the grown-up version. No weapons, no cheat code. Just a pile of tools for the job in front of you, whether that is converting a photo or fixing a JSON file at 11 p.m.

What is live today

  • Image tools convert between 20+ formats (including HEIC from iPhones and RAW files), compress, resize, and optimize, in batch, with every codec running locally.
  • Encoding, generator, crypto, JSON, and web tools cover base64 and URL encoding, passwords and UUIDs, hashes, JSON formatting, and JWT inspection. Same rule: nothing leaves the tab.
  • Time tools cover timestamp and timezone conversion, duration math, and availability sharing, all computed in the page.
  • Video and audio tools convert, compress, trim, resize, normalize, and merge media in the browser, with the same local-processing rule.

Why I built it this way

Most online converters ask you to upload private files to a stranger's server, then wait in a queue behind everyone else. I think that trade is backwards. A modern browser is a capable computing platform: WebAssembly runs real, battle-tested codecs (the same ones behind tools like FFmpeg) at native-adjacent speed. Once a Nutter Tools page and its engine code have loaded, it keeps working offline, on a plane or on locked-down networks, and your files stay yours. That design also means there is no account to create, no quota tied to your email, and no file retention policy to trust. There is simply nothing retained.

The trade-offs, honestly

Client-side processing is bounded by your device. Very large files depend on your browser's memory limits, and speed depends on your CPU rather than a server farm. There is no public file-processing API and no server-side batch mode. If you need to process thousands of files programmatically, a command-line tool like FFmpeg is the better fit. For one image or a folder of them, Nutter Tools trades a queue for privacy.

Where to go next

  • Start with the image tools or browse every page on the site.
  • Agents and crawlers: /llms.txt describes the site and when to use it; /sitemap.xml lists every indexable page.
  • Questions, privacy, or legal matters: see contact.