Quick answer
Beyond your editor and terminal, the small tools developers use most are formatters and validators (JSON, SQL, HTML), a regex tester, a diff checker, encoders and decoders (Base64, URL, JWT), generators (UUIDs, hashes, mock data), converters (timestamps, CSV to JSON, cron expressions) and diagramming tools for systems and databases. Keep a trusted set bookmarked, and never paste secrets into a tool you haven't vetted.
A lot of development time goes into small, fiddly tasks: working out why a JSON payload won't parse, checking what a token contains, comparing two config files, converting a timestamp from a log. Single-purpose utilities turn those minutes into seconds. This guide groups the most useful ones by job, explains what to watch out for, and points to free browser-based versions.
In this article
The everyday toolkit at a glance
| Task | Tool | Typical use |
|---|---|---|
| Read or fix JSON | JSON formatter / validator | Pretty-print an API response; find a syntax error |
| Test a pattern | Regex tester | Check a validation rule against real input |
| Compare text | Diff checker | Spot changes between two configs or responses |
| Tidy a query | SQL formatter | Make a long generated query readable |
| Inspect a token | JWT decoder | Check claims and expiry while debugging auth |
| Encode data | Base64 / URL encoder | Debug headers, query strings and data URIs |
| Generate IDs | UUID generator | Test fixtures, database seeds |
| Convert time | Unix timestamp converter | Read dates in logs and databases |
| Read a schedule | Cron expression parser | Confirm when a job will really run |
| Plan a system | Flowchart / ERD / data-flow tools | Design reviews, documentation, onboarding |
Formatters and validators
Minified JSON, one-line SQL from an ORM and unindented HTML are hard to read and harder to debug. A formatter adds structure; a validator tells you exactly where the syntax breaks — usually a trailing comma, a missing quote or an unescaped character.
Try the free JSON FormatterBeautify, minify and validate JSON, with clear error locations.Try the free SQL FormatterFormat SQL in many dialects or compare two versions of a query.See also: how to format JSON and fix common errors.
Regex testers and diff checkers
Regular expressions are easy to get almost right. Test them against real examples — including ones that shouldn't match — and check capture groups before you ship. Remember that regex flavours differ slightly between languages.
Try the free Regex TesterLive match highlighting and groups as you type.A diff checker answers “what changed?” when you don't have version control to hand: two API responses, an environment file from staging and production, a contract revision.
Try the free Diff CheckerCompare two texts side by side and see every added, removed and changed line.Encoders, decoders and tokens
Base64 and URL encoding come up constantly in headers, query strings and data URIs. A JSON Web Token (JWT) is three Base64URL-encoded parts — header, payload and signature — so its claims can be read by anyone who has it.
Try the free JWT DecoderRead a token's header and payload and check its expiry.Try the free Base64 Encoder & DecoderEncode or decode Base64, UTF-8 safe.Our article Are online file tools safe? shows how to check whether a tool uploads your data.

Generators and converters
- UUIDs for test data and identifiers that must not collide.
- Hashes (SHA-256 and others) to compare files or check downloads. For storing passwords, use a dedicated password-hashing algorithm such as bcrypt, scrypt or Argon2, not a plain hash.
- Mock data to fill a UI or test an API without real customer information.
- Unix timestamps — seconds (or milliseconds) since 1 January 1970 UTC — are everywhere in logs. See what a Unix timestamp is.
- CSV to JSON when spreadsheet data needs to become an API payload or fixture.
- Cron expressions: a parser that lists the next run times catches the classic “it runs at midnight UTC, not local time” mistake.
Diagramming and documentation
Diagrams make design reviews faster and onboarding easier. A flowchart explains logic, a data-flow diagram shows how information moves between systems, and an entity-relationship diagram documents a database schema. Keep them next to the code and update them when the design changes.
Try the free ERD MakerDesign database diagrams with crow's-foot relationships, import SQL and generate it back.Read more: how to visualize database relationships.
Build a toolkit you trust
- Bookmark a small set and use the same ones, so you know how they behave.
- Prefer tools that run locally — in your browser or as a CLI — for anything sensitive.
- Learn your editor's built-ins: many formatters, diff views and regex search are already there.
- Keep a personal cheat sheet of commands and snippets you look up repeatedly — see our JavaScript cheat sheet for an example.
Frequently asked questions
What tools should every developer have?
A good editor and terminal, version control, and a set of small utilities: a JSON formatter and validator, a regex tester, a diff checker, encoders and decoders, a timestamp converter and a diagramming tool.
Is it safe to paste a JWT into an online decoder?
Only if you trust the tool and it decodes locally in your browser. JWT payloads are readable by anyone, and a valid production token can grant access, so avoid pasting live tokens into unknown sites.
Is Base64 encryption?
No. Base64 is a reversible encoding for representing binary data as text. Anyone can decode it, so it provides no security.
Should I hash passwords with SHA-256?
No. Use a dedicated password-hashing algorithm such as bcrypt, scrypt or Argon2, which are deliberately slow and salted to resist cracking.



