I got tired of online JSON tools crashing on syntax errors and conversions, so I built a local-first repair engine

#privacy #software #tools #webdev

Every developer uses online JSON formatters daily to debug API responses, inspect log files, or check database dumps.

But standard JSON formatters come with two recurring papercuts:

Parser Fragility: Standard JSON.parse is unforgiving. A single trailing comma, missing quote, or Python-style True/False boolean completely crashes the formatter, forcing you to fix it manually character by character.
Data Privacy Risks: Pasting production payloads, JWTs, or environment variables onto unencrypted, third-party server-side formatters is a security risk waiting to happen.

To solve both issues for my own workflow, I built MyJSONPal—a 100% client-side JSON studio designed for speed, privacy, and auto-repair.

⚡ 1. Magic AST Auto-Repair

Instead of failing on malformed JSON, MyJSONPal uses a client-side parsing engine that automatically cleans common syntax issues before formatting:

Trailing Commas: Strips trailing commas from arrays and objects.
Quote Normalization: Converts single-quoted strings and unquoted object keys into valid double-quoted JSON.
Language Equivalents: Automatically normalizes Python booleans (True/False) and None values into standard JSON syntax (true/false/null).

🔒 2. 100% In-Browser Privacy

Security shouldn't be an afterthought when inspecting API responses.

MyJSONPal runs entirely in your browser. There are zero server network calls, zero tracking logs, and zero remote data stores. Your production payloads and tokens never leave your local machine.

🛡️ 3. One-Click Type & Schema Generation

When integrating APIs, formatting the JSON is only step one. You usually need type definitions next.

MyJSONPal instantly infers:

Zod Schemas: Generates ready-to-use z.infer schemas for immediate runtime validation.
TypeScript Interfaces: Converts raw payloads into clean TS types.
Data Exports: Converts JSON directly to CSV (RFC 4180 compliant) and YAML.

Additional Core Features

Beyond the AST Auto-Repair, Client-Side Privacy, and Type Generation already covered, here are the additional core features built into MyJSONPal that make it a complete JSON workbench.

1. Advanced Structural Transformations

Recursive Key Sorting
- Instantly sorts all keys in nested objects alphabetically (A–Z or Z–A) to standardize payloads before committing or comparing.
Smart Minification & Formatting
- Switch between minifying payloads into a single line for API calls or formatting them with customizable tab or space indentation.
Key Extraction & Dot-Notation
- Flatten complex nested structures and extract all keys along with their precise dot-notation paths (e.g., user.profile.settings.theme).

2. Deep Data Conversion Pipeline

Bi-directional Conversions
- Convert JSON seamlessly into YAML, CSV (RFC 4180), or XML, and vice versa.
Base64 & Stringify Tools
- Decode Base64 payloads (such as JWTs) directly into structured JSON, or escape raw JSON into stringified literals ready for use in code variables.

3. Visual Exploration & Search

Interactive Collapsible Tree View
- Navigate massive multi-megabyte payloads with expandable and collapsible nodes, making it easy to inspect deeply nested responses.
Live Search & Path Finder
- Search for specific keys, values, or array indices across large datasets without slowing down the editor.

4. Performance & UX Foundations

Web Worker Architecture
- Heavy processing runs inside isolated background threads, keeping the UI responsive even when working with large database exports.
Shared Workspace State
- Paste your JSON once and switch between validators, converters, and generators without losing your input or re-uploading files.
VsCode Styled Editor
- Enjoy syntax highlighting, error-line navigation, dark/light theme support, and offline-first functionality.

🚀 Try It Out

It's completely free to use with no account required:

👉 myjsonpal.com

I’d love to hear your feedback! What JSON edge cases or converter options would make your daily debugging workflow easier? Let me know in the comments below!

Top comments (1)

Aftan Ahmad • Aug 1

Thanks for reading! I'm actively monitoring this post—let me know if you hit any edge cases with the parser or have suggestions for new target schema exports!