Data

Data

Browse 21 professional tools

Base64 Encoder & Decoder

Data

Braille Translator

Data

Chart Builder

Data

Data Converter

Data

Data Table Editor

Data

Database Schema Designer

Data

Decision Wheel Spinner

Data

IBAN Validator

Data

JSON Tree Diff

Data

Morse Code Translator

Data

NATO Phonetic Alphabet

Data

NIP & PESEL Validator

Data

Number Base Converter

Data

Random Data Generator

Data

Roman Numeral Converter

Data

State Machine Designer

Data

Text to Binary/Hex Converter

Data

Typing Speed Test

Data

Unit Converter

Data

UUID Generator

Data

VIN Decoder

Data

Data tools cover format conversion, ID generation, and document validation. The interesting axis is "structural" (JSON/XML/CSV/YAML conversion preserves the tree shape) vs "encoding" (base64/binary/morse/braille rewrite the bytes). All run locally; safe for production payloads and PII.

Identifiers

UUID v7 (timestamp-prefixed, sortable, RFC 9562, 2024) is the default for new database primary keys; v4 stays useful for opaque IDs. IBAN / NIP / PESEL / VIN validators use the official checksum algorithms; random data generator outputs locale-realistic fake data using RFC 6761 reserved domains.

Encoding & conversion

Format-to-format conversion (JSON ↔ YAML ↔ XML ↔ CSV ↔ TOML) with format-specific edge cases surfaced as warnings (YAML "Norway problem", CSV BOM, XML namespaces). Number base conversion handles arbitrary bases up to 36; binary/hex shows multiple character encodings side by side.

Specialized translators

Morse with PARIS-standard WPM measurement, NATO/ICAO phonetic alphabet for telephone clarity, Unicode Braille (U+2800-U+28FF) with Grade 1 and Grade 2 English UEB support.

Spreadsheet & database

Browser spreadsheet for ad-hoc data work, visual ERD editor for database schemas (with UUID v7 defaults and money-as-cents conventions), structural JSON diff that ignores key ordering, finite state machine designer exporting XState.

Frequently asked questions

Why does my JSON-to-YAML conversion lose comments?

JSON has no comment syntax. Round-trip JSON → YAML → JSON drops any comments in the intermediate YAML. To preserve commentary, keep the YAML source-of-truth and only generate JSON for consumption. Same applies to TOML and other formats with comments.

Should I use UUID v4 or v7 for primary keys?

v7 if your database uses B-tree indexes (Postgres, MySQL, SQLite — all of them). v4 inserts in random index positions, fragmenting the tree and slowing writes. v7 inserts sequentially like an auto-increment integer. The 2024 RFC 9562 standardized v7; libraries in every major language support it.

How do I validate a Polish PESEL?

Multiply digits 1-10 by weights 1,3,7,9,1,3,7,9,1,3, sum mod 10, subtract from 10 (with 10→0 special case). The result is the check digit. The NIP/PESEL Validator does this plus extracts date of birth and sex from the structure.

Is the random data really random?

Uses crypto.getRandomValues — the same source as TLS key generation. For test fixtures it is overkill; for production randomness (tokens, passwords) it is the right level. Math.random is predictable from a small sample and should never be used for security-sensitive purposes.

Last updated · E-Utils editorial team