Home

Developer workbench

Data workbench

One page for the data chores you repeat: JSON, CSV, YAML, URL encoding, Base64, and hashing. Each mode reuses the same local libraries as the dedicated tool pages.

Mode

Workbench mode

Input

Input

Output

Output

What this combines

JSON formatting/validation, CSV↔JSON, YAML↔JSON, URL encode/decode, Base64, and SHA hashes share one workspace so you can switch modes without opening five tabs. Base64 now lives here; the old /tools/base64-encode-decode/ URL redirects to this page.

Privacy

All modes run in the browser. Input is not uploaded to modu.tools.

The data workbench puts six routine developer tasks on one page: JSON format and validate, CSV to JSON, YAML to JSON and back, URL encode and decode, Base64, and SHA hashing. Pick a mode, paste input, copy output. You do not need a stack of tabs, and nothing is uploaded.

What each mode is for

Mode Job Dedicated page
JSON Indent, minify, validate JSON formatter
CSV→JSON Delimiter detection, objects or arrays CSV to JSON
YAML↔JSON Both directions YAML/JSON
URL Percent-encoding URL encode/decode
Base64 UTF-8 text ↔ Base64 (workbench)
SHA hash SHA-1, 256, 384, 512 Hash generator

Dedicated pages carry longer explanations. The workbench is better when you chain steps: CSV to JSON, then JSON format, then hash a snippet.

Example: encode a query value

A search term with a space and an ampersand breaks a URL if pasted raw. In URL mode, 서울 맛집&page=2 becomes a percent-encoded value where & and = are escaped, so the server treats it as one parameter instead of inventing another page field.

Example: Base64 for UTF-8 text

모듈 is 6 bytes in UTF-8 and becomes 8 Base64 characters. Anyone can decode it. Use Base64 to embed awkward bytes in logs or JSON—not to hide passwords. For the conceptual split between Base64, hashing and encryption, see the site guides on those topics.

Example: CSV sample then JSON inspect

Paste a small CSV sample, convert to JSON, switch to JSON mode and indent. Korean-only headers may normalize to column_N keys—that is the CSV tool rule, not a random bug. Prefer English headers or array mode when you need stable keys.

Safety

Local computation still leaves paste buffers, screen shares and extensions in play. Do not paste production passwords, personal data or live API keys. Use masked fixtures.

What is not in the workbench

Image crop/resize lives on the image tool. Character counting, romanization and Markdown tables have their own pages. This workbench is the text data conversion bench.

Two useful chains

Chain 1: tabular sample → API fixture. Convert CSV to JSON objects, switch to JSON mode to indent, then trim fields for the doc. Use the dedicated JSON page when you also need alphabetical key sorting.

Chain 2: config → fingerprint. Convert YAML to JSON, then hash with SHA-256. Share only the digest in chat and keep the source in the repo so people do not paste secrets into random tabs.

Copy anything you need before switching modes. Clear the input when you are done.

FAQ

Is my input sent to a server?

No. Every mode runs in this browser tab. Formatting, conversion, encoding and hashing happen locally and are not uploaded to modu.tools.

Why does Base64 output for non-English text look longer than I expect?

The workbench encodes text as UTF-8 before Base64. A Korean syllable takes 3 bytes in UTF-8, so two syllables become 6 bytes and 8 Base64 characters.

Is Base64 encryption?

No. Base64 is reversible encoding for moving bytes through text-only channels. It does not protect secrets.

Does switching modes clear my input?

Modes share the workspace pattern on this page. Copy anything you need before switching, and clear sensitive paste buffers when you finish.