One-off tasks don't deserve npm packages
Every developer knows the pattern: a two-second task — pretty-print some JSON, decode a JWT-looking string, convert a CSV — and suddenly there's a global package installed that you'll never use again. FileForge's text and developer utilities cover the common ones in a tab, computing locally like a CLI would.
Data shape-shifting
- JSON Formatter — validate, beautify and minify config blobs and API responses.
- CSV ↔ JSON — fixture data and migrations without pandas.
- XML Formatter — legacy SOAP payloads and pom.xml diffs.
- Base64 Encoder/Decoder — headers, tokens and data URIs.
Verification and identity plumbing
- File Hash — confirm a download matches its published checksum before running it.
- UUID Generator — bulk test IDs via the browser's cryptographic randomness.
- Password Generator — throwaway credentials for staging environments.
Text wrangling
- Text Diff — spot the difference between two config versions without committing anything.
- Case Converter — snake_case to camelCase to kebab-case in one paste.
- Word Counter/Character Counter — commit message and changelog length checks.
Why local matters even for "harmless" data
Tokens, internal endpoints and customer names sneak into supposedly harmless snippets. Paste-based web tools transmit everything you paste to their servers; FileForge's tools operate purely in page memory. Same workflow you'd trust a CLI with, zero installation.
ZIP without the shell
Create ZIP and Extract ZIP handle archives in the browser too — convenient on machines where you'd rather not unpack arbitrary archives to disk unreviewed. Pair extraction with File Inspector to see what an archive actually contains before opening its contents elsewhere.