Developer tools | agent view
The same page content and links, with explicit tool capabilities. Tools marked with an API can run directly through HTTP. Other tools require the browser interface or are not connected yet.
Page guide
Find the tool you need, then open it to get started.
All developer tools
ASCII to text
Decimal/hex ASCII codes and explicit distinction from Unicode.
Base64 encoder decoder
Encode/decode tabs.
Bcrypt generator
Generate and verify locally with work-factor control.
Binary to text
Decode binary byte values into UTF-8 text.
Chmod calculator
Numeric and symbolic Unix permission mapping.
Cron parser
Cron dialect and time-zone selection.
CSS formatter
Format/minify CSS with parser-based errors.
CSS inliner
Inline supported selectors for email HTML.
CSS minifier
Pinned parser with source-size comparison and downloadable output.
Curl to code
Parse quoting, headers and body.
File hash
SHA-256 digest and compare expected value.
Hex to text
Decode hexadecimal byte values into UTF-8 text.
HMAC generator
Local keys and data.
HTML escape
Escape/unescape modes.
HTML formatter
Format/minify with options.
HTML minifier
Configurable safe whitespace/comment treatment.
Javascript formatter
Parse and format code without executing it.
Javascript minifier
Syntax-target selection.
Jq playground
Run pinned jq version with resource limits.
JSON diff
Structural rather than textual comparison.
JSON escape
Escape/unescape string literals with visible control-character handling.
JSON formatter
Format and validate JSON in your browser.
JSON schema validator
Dialect-aware validation with exact instance paths and local reference resolution.
JSON to go
Struct tags, names, nullable fields and number-type options.
JSON to java
Class naming, lists, nullability and numeric precision options.
JSON to python
Dataclass or TypedDict output.
JSON to schema
Choose schema dialect.
JSON to typescript
Infer types from samples with optional properties and unions.
JSON validator
Line/column errors and clear syntax-versus-schema validation scope.
Jsonpath tester
Show matched paths and values.
JWT decoder
Decode header/payload locally.
Mock data generator
Schema-driven seeded synthetic CSV/JSON.
Number base converter
Binary/octal/decimal/hex with large-integer precision and signed-number rules.
Regex tester
Declare JavaScript flavor and flags.
RSA key generator
Local cryptographic RNG and formats with interoperability review.
SQL formatter
Select dialect and format without executing queries.
Token counter
Explicit model/tokenizer version.
Unix timestamp converter
Seconds versus milliseconds, UTC/local zones and explicit out-of-range handling.
URL encoder decoder
Encode or decode a URL component.
URL parser
Show scheme, host, port, path, query and fragment.
URL to punycode
Unicode domain and ASCII conversion with IDNA version stated.
UUID generator
Declare UUID versions, secure randomness for v4 and batch copy/export limits.
XML formatter
Pretty-print/minify with safe parsing and explicit mixed-content handling.
XML validator
Well-formedness validation.
YAML formatter
Pin YAML version.
YAML validator
Line/column errors, duplicate-key policy and safe parsing without arbitrary constructors.
Format, validate and transform are different tasks
Formatting makes existing data or code easier to read. Validation checks whether it follows a syntax or schema. Conversion maps it into another representation. Choosing the right operation helps avoid treating a neatly formatted result as proof that the underlying data is correct.
How to choose your next step
Start with a small representative sample. Confirm the syntax or language variant, then inspect errors and edge cases before applying the same operation to a larger input.
Common questions about developer tools
Does valid JSON mean the data is correct?
Syntax validation only establishes that the text can be parsed as JSON. A schema can check required fields and types, but neither proves that an email address, price or external record is factually correct.
Is decoding the same as decrypting or verifying?
No. Base64 and URL encoding are representations, not encryption. Reading a token payload does not verify its signature. Use the specific validation or verification process required by the system receiving the result.