Frequently asked questions

You can create sample records in JSON, CSV, or SQL format using your own field schema. Supported field types include names, emails, phone numbers, addresses, dates, numbers, and UUIDs.

Yes. It is useful for demos, test datasets, UI prototypes, and development environments that need realistic-looking data without touching production records.

You can generate up to hundreds of rows per run. For large datasets needed repeatedly, exporting and using the data locally is the recommended approach.

No. The tool is browser-based. Your field configuration and generated output are never sent to any external server.

Mock Data Generator outputs JSON, CSV, and SQL INSERT statements. You can copy the result directly or download it as a file.

The SQL formatter supports PostgreSQL, MySQL, Oracle, and generic SQL. Select the right dialect before formatting to get dialect-specific keyword handling.

Use it when you receive a one-line minified query from a log, need to clean queries before a code review, or want to inspect a complex JOIN statement more clearly.

No. The tool formats syntax only and does not execute or validate your SQL. Syntax errors in your query will not be caught by the formatter.

No. SQL formatting runs entirely in your browser using the sql-formatter library. No query data leaves your machine.

Yes. The formatter handles multi-statement SQL including stored procedures, CTEs, and scripts with multiple queries separated by semicolons.

It converts JSON into TypeScript interfaces with correct types inferred from your data — string, number, boolean, arrays, and nested objects are all handled automatically.

Type Generator supports TypeScript interfaces, Go structs, and Java classes. Select the target language before converting your JSON.

Yes. Nested objects are recursively converted into separate interface or struct definitions, keeping the output clean and idiomatic for each language.

Yes. Paste a real API response and get a typed model immediately. It is especially useful when integrating a third-party API without an SDK.

No. Type generation runs entirely in your browser. Your JSON payload is never uploaded anywhere.

It generates strong passwords, API keys, and JWT secrets using the browser Crypto API for cryptographically secure randomness.

Yes. Password generation supports optional numbers and special characters. You can configure length and character set to match your requirements.

Yes. The tool uses window.crypto.getRandomValues(), the same cryptographic randomness API used by browsers for TLS. Outputs are not predictable.

A JWT HS256 secret should be at least 32 bytes (256 bits). This tool generates secrets at the right length by default.

No. Everything runs in your browser. Generated secrets are never transmitted to any server, logged, or stored.

It takes minified or unformatted JSON and outputs a readable, indented version with consistent spacing. This makes it easy to find missing fields, wrong types, or unexpected nesting.

Use it when you receive a minified API response in a log, need to inspect a large payload quickly, or want to validate that a JSON string is well-formed before using it.

Yes. The tool reports a parse error if your input is not valid JSON. This makes it useful as a quick JSON validator as well as a formatter.

Yes, for files up to a few MB. Very large files may be slow to process in the browser. For consistently large files, consider a CLI tool like jq.

No. JSON formatting is performed entirely in your browser using native JavaScript. No data is transmitted to any external server.

Compact JSON is JSON with all unnecessary whitespace removed so that the same data takes up less space. It is the opposite of pretty-printed or formatted JSON.

They refer to the same thing: removing indentation and line breaks so the JSON fits on a single line. Some tools also let you strip null fields or sort keys as additional compaction steps.

No. Removing whitespace and sorting keys do not change any values. Stripping null fields does remove keys whose value is null, so enable that option only when null fields are intentionally absent.

Yes. Compact JSON runs entirely in your browser. No data is sent to any server.

It removes all unnecessary whitespace, line breaks, and indentation from JSON to produce the smallest valid representation of the same data.

Minified JSON reduces payload size for API responses, reduces storage costs, and decreases page weight when embedding JSON in HTML script tags.

No. Minification only removes whitespace. The actual data — keys, values, structure — is completely unchanged.

Yes. Any valid formatted JSON produces valid minified JSON. The two representations are semantically identical.

No. JSON minification runs in your browser. No data is uploaded or sent anywhere.

It takes minified or unindented XML and outputs a clean, indented structure. Each nested element is visually separated, making the document hierarchy immediately readable.

Use it when working with SOAP API responses, RSS or Atom feeds, Android layout files, Maven POM files, or any other XML that arrives as a single unreadable string.

The tool reports parse errors for malformed XML. It checks structural well-formedness but does not validate against an XSD schema.

Yes. Namespace declarations and prefixed elements are preserved exactly as-is during formatting.

No. XML formatting runs entirely in your browser. Your data never leaves your machine.

Base64 is an encoding scheme that represents binary data as printable ASCII characters. It is commonly used in data URIs, email attachments, and API payloads.

No. Base64 is encoding, not encryption. It changes how data is represented, not how it is protected. Anyone with the Base64 string can decode it.

No. This tool runs entirely in your browser. No data is transmitted anywhere.

It is useful when embedding binary data in text-based formats like JSON, XML, HTML, or HTTP headers, where raw binary would be unsafe or unsupported.

Base64-encoded data is approximately 33% larger than the original. Every 3 bytes of input becomes 4 characters of Base64 output.

URL encoding replaces special characters with percent-encoded sequences so they can be safely included in URLs. For example, a space becomes %20 and & becomes %26.

Component encoding (encodeURIComponent) escapes all special characters including /, ?, and &, making it suitable for query parameter values. Full URL encoding (encodeURI) preserves structural characters like /, ?, and & that have meaning in the URL.

No. This tool processes everything client-side in your browser. Nothing is sent to any server.

Use it when building query strings, debugging encoded API endpoints, or when you receive a URL with percent-encoded characters and need to read it clearly.

Form data (application/x-www-form-urlencoded) uses + for spaces, while RFC 3986 percent-encoding uses %20. This tool uses standard percent-encoding (%20) which is safe in all contexts.

This tool generates UUID version 4 identifiers using browser cryptographic randomness from window.crypto.randomUUID().

Yes. You can generate UUIDs in bulk and copy them all in one click, ready to paste into code, config, or a database.

UUID v4 is a randomly generated 128-bit identifier following RFC 4122. It has 2^122 possible values, making collisions practically impossible for application-level use.

With overwhelming probability, yes. UUID v4 collision probability is negligible for any practical application. The format is widely used for database primary keys, event IDs, and session tokens.

Yes. GUID (Globally Unique Identifier) is Microsoft's term for the same standard. UUID and GUID are interchangeable in most contexts.

The tool supports SHA-256 and SHA-1 using the browser SubtleCrypto API. An MD5 compatibility reference is included for legacy interoperability guidance.

No. Hashing is a one-way function. It is computationally infeasible to recover the original input from a hash output.

SHA-256 is used for file integrity verification, API request signing (HMAC-SHA256), password hashing (combined with a salt), and content fingerprinting.

MD5 has known collision vulnerabilities and should not be used for security-critical purposes. It is still sometimes used for non-security checksums like cache keys or ETags.

No. Hashing runs entirely in your browser using the Web Crypto API. No data is uploaded or transmitted.

Yes. Unix input is auto-detected as seconds (10 digits) or milliseconds (13 digits) based on magnitude.

Unix-to-date conversion outputs ISO 8601 UTC timestamps (e.g. 2024-01-15T10:30:00.000Z) for clarity and cross-system compatibility.

A Unix timestamp is the number of seconds (or milliseconds) elapsed since January 1, 1970 at 00:00:00 UTC. It is the standard time representation for APIs, databases, and log files.

Paste your date string in ISO 8601 format or a common locale format into the date field and the tool will output the corresponding Unix seconds and milliseconds.

The year 2038 problem affects 32-bit systems where Unix timestamps overflow at 2147483647 (January 19, 2038). Modern 64-bit systems are not affected.

No. This tool decodes the JWT header and payload only. It does not validate the signature, expiry, or issuer. For security-critical verification, use a proper JWT library.

No. The token is decoded entirely in your browser using Base64 decoding. No token data is transmitted anywhere.

You can inspect all standard claims including iss (issuer), sub (subject), aud (audience), exp (expiry), iat (issued at), and any custom claims in the payload.

The exp claim is a Unix timestamp. Compare it to the current time to determine if the token has expired. The decoder shows the raw exp value you can check.

The decoder reads any JWT regardless of algorithm (HS256, RS256, ES256, etc.) since it only decodes the header and payload, not verifies the signature.

camelCase, PascalCase, snake_case, kebab-case, SCREAMING_SNAKE_CASE, and Title Case are supported.

Yes. The converter normalizes words from any input format and generates each output style from your input text.

camelCase starts with a lowercase letter (myVariable), while PascalCase starts with an uppercase letter (MyVariable). PascalCase is commonly used for class and component names.

snake_case (with underscores) is standard in Python and database column names. kebab-case (with hyphens) is standard in CSS class names and URL slugs.

No. All conversion runs client-side in your browser. No input text is transmitted anywhere.

A cURL converter takes a cURL command — the kind you copy from browser DevTools or API documentation — and outputs equivalent HTTP client code in your language of choice. No manual translation needed.

The converter outputs Python (requests), JavaScript (fetch), JavaScript (axios), Go (net/http), PHP (curl), and Ruby (net/http). Select the target language before converting.

The parser handles -X (method), -H (headers), -d/--data (body), --user (Basic Auth), --oauth2-bearer (Bearer token), --cookie, --insecure, -L (follow redirects), and --max-time (timeout).

In Chrome or Firefox DevTools, open the Network tab, right-click any request, and choose "Copy → Copy as cURL". The result can be pasted directly into this converter.

No. All parsing and code generation runs client-side in your browser. Your cURL commands — which may contain credentials or tokens — never leave your machine.

It performs a deep comparison between two JSON objects and highlights every field that was added, removed, or changed. The result is a visual tree with color-coded differences.

Green means a field was added in JSON B. Red means a field was removed from JSON A. Yellow means a value was changed. Unchanged fields are shown in the default text color.

Yes. The diff is recursive: nested objects are compared field by field, and arrays are compared element by element with index-based alignment.

Yes. Top-level arrays are fully supported. Each element is compared at the same index, and elements added or removed are flagged accordingly.

No. The diff algorithm runs entirely in your browser. Neither JSON A nor JSON B is transmitted anywhere.

A regex tester lets you write a regular expression and immediately see which parts of your test text it matches, including capture group values and match positions.

The tester supports the standard JavaScript regex flags: g (global), i (case-insensitive), m (multiline), s (dotAll), u (unicode), and y (sticky). Toggle them with the flag buttons.

It breaks your regex into tokens and explains each one in plain English — for example, \d+ is explained as "one or more digit characters".

Yes. The match table shows each match with its full value, all numbered capture groups, and the start and end index in the test string.

No. All matching runs client-side using the browser's native JavaScript RegExp engine. Nothing is transmitted anywhere.

JSON Schema is a vocabulary for describing the structure of JSON data. A validator checks whether a JSON document conforms to a schema, reporting exactly which fields fail and why.

The validator supports the core keywords from JSON Schema draft-07: type, properties, required, additionalProperties, items, minLength, maxLength, minimum, maximum, pattern, enum, const, allOf, anyOf, oneOf, and not.

Each error includes the JSON path to the failing value (e.g. $.user.age) and a human-readable message describing the constraint that was violated.

Yes. The validator recurses through all nested objects and arrays, reporting errors at the exact path where each violation occurs.

No. Validation runs entirely in your browser. Neither the schema nor the JSON document is uploaded or transmitted anywhere.

A cURL generator lets you fill in HTTP request parameters — URL, method, headers, body, authentication — using a form, and produces a ready-to-run curl command without needing to memorize flag syntax.

The Linux/macOS output uses standard curl syntax with backslash line continuations. The PowerShell output uses Invoke-WebRequest, the native PowerShell cmdlet, with backtick continuations and @{} header hashtables.

Copy the Invoke-WebRequest command and paste it directly into a PowerShell terminal (Windows PowerShell 5.1+ or PowerShell 7+). No extra tools needed — Invoke-WebRequest is built into PowerShell.

Yes. Use the Headers section to add any number of key-value header pairs. Common headers like Content-Type and Authorization are also set automatically when you choose a body type or auth method.

No. The cURL command is generated entirely in your browser. None of your URL, credentials, or payload is transmitted anywhere.