Resource guide
Developer utilities online
JSON/YAML/XML helpers, Base64 and URL encoders, cryptographic hashes, UUIDs, timestamps, and QR utilities—structured for quick keyboard workflows.
Developer workflow notes
Developers live in snippets: pretty-printing chaotic logs, diffing configs, proving checksums, generating correlation IDs. Desktop CLIs excel in pipelines, but browser tabs win during pairing calls when screen sharing means everyone needs identical visuals without syncing dotfiles.
Encoding utilities clarify subtle bugs—double-encoded URLs, newline-corrupted Base64 from chat apps, mismatched MIME headers. Hash generators document release artifacts or verify downloads when CI publishes checksum files alongside binaries.
Time tooling spans Unix epochs, time zones for on-call rotations, and occasional QR payloads for staging endpoints. CSV ↔ JSON bridges tie into data-engineering habits already covered in the office hub but surfaced here for API-focused practitioners.
Security mindfulness still applies: treating browser tabs as scratch pads is fine for synthetic data; rotate secrets if accidental paste occurs and never rely on client-side hashing for production secret storage.
Workflows
Browse developer utilities
JSON & structured data
Hashes & identifiers
Time, date & QR utilities
Tabular interchange
Every tool in this guide
Full directory sorted alphabetically.
Barcode generator
Use Barcode generatorBase64 decode
Use Base64 decodeBase64 encode
Use Base64 encodeBase64 encoder / decoder
Use Base64 encoder / decoderCSV to JSON
Use CSV to JSONCSV to SQL
Use CSV to SQLHash generator (MD5, SHA-1, SHA-256, SHA-512)
Use Hash generator (MD5, SHA-1, SHA-256, SHA-512)JSON formatter (converters path)
Use JSON formatter (converters path)JSON formatter & validator
Use JSON formatter & validatorJSON to CSV
Use JSON to CSVJSON to YAML
Use JSON to YAMLJSON tools hub
Use JSON tools hubJSON viewer
Use JSON viewerMD5 hash
Use MD5 hashQR code generator
Use QR code generatorQR code reader
Use QR code readerSHA-1 hash
Use SHA-1 hashSHA-256 hash
Use SHA-256 hashTime & date converters hub
Use Time & date converters hubTimezone tools
Use Timezone toolsUnix timestamp converter
Use Unix timestamp converterURL encoder / decoder
Use URL encoder / decoderUUID generator
Use UUID generatorYAML to JSON
Use YAML to JSONComplete tool index
Alphabetical list of every tool on this hub. Each row links to the dedicated tool page—useful for scanning and site discovery.
About browser developer helpers
Encoding & data utilities
- Why does Base64 length explode versus raw binary?
- Encoding expands roughly 4:3 plus newline penalties depending on MIME wrapping. Size alarms in CI logs usually trace to accidental double-encoding—decode once, verify magic bytes, then re-encode.
- UUID v4 versus v1 in browser generators?
- v4 is pure randomness; v1 embeds timestamp + MAC-derived bits when libraries emulate RFC nodes. Pick v4 for opaque IDs unless you sort lexically by creation time.
- SHA-256 mismatch despite identical files—what checks first?
- Line endings (CRLF vs LF), trailing spaces, or streamed chunk ordering can differ while editors show identical text. Hash raw bytes from disk, not clipboard paste buffers.
- JSON formatter says valid—but API rejects it?
- Trailing commas, single quotes, or BOM prefixes survive casual editors yet violate strict JSON. Run through the formatter linked here, then diff hex headers if parsers still disagree.