25 developer tools worth bookmarking

September 27, 2026 · 15 min read

Scattered bookmarks slow you down. A short, maintained list of tools you trust beats searching “online json formatter” every sprint. This roundup focuses on utilities that run in the browser, respect privacy, and cover the formats backend and full-stack developers touch daily.

JSON tools (format, validate, compare, minify)

JSON formatter - readable trees from minified log lines.
JSON validator - catch syntax errors before CI.
JSON compare - structural diff for API regressions.
JSON minifier - shrink fixtures for tests and docs.
JSON Path / query helpers - explore large documents quickly.

Auth, JWT, and encoding

JWT decoder - inspect claims without uploading tokens.
JWT generator - learn signing with sample keys.
Base64 encode/decode - debug legacy payloads.
URL encoder - fix query strings and redirect bugs.
Hash generators - verify checksums in support tickets.

HTTP and headers

Header parsers break down Content-Type, Authorization, and Cookie values. User-agent parsers help reproduce mobile bugs. Keep cURL and httpie docs bookmarked too - they are not browser tools but complete every API toolkit.

IDs and identifiers

UUID generator - v4 and v7 for tests and fixtures.
UUID validator - version and variant checks.
MongoDB UUID converter - subtype 03 vs 04 byte order.
Timestamp converters - align logs across time zones.

How to organize bookmarks

Use one folder per concern (JSON, Auth, HTTP, IDs) or a single “Dev tools” folder with a pinned hub page. Review quarterly - remove dead links and duplicates. Share the folder export with new hires so everyone uses the same validators and decoders.

FAQ

How many tools should I actually bookmark?: Five to ten you use weekly, plus one hub page for the rest. Too many bookmarks become another search problem.
Why browser tools instead of desktop apps?: Zero install, easy sharing in pair sessions, and often client-side processing for sensitive data.
Should teams maintain a shared bookmark list?: Yes - a short internal doc or wiki link reduces 'which formatter do you use?' friction.

Browse all tools