JSON Bay

A simple and user-friendly online JSON editing toolkit

Overview

JSON Bay is an online JSON editing and conversion tool.

You can easily convert Excel (spreadsheet) data into JSON format and compress JSON data using multiple methods.

While there are many JSON formatting and conversion sites available, many have outdated designs or difficult-to-use UIs. I created JSON Bay to be the online JSON editing tool I wanted to use myself.

What Inspired Me to Create It

In the past, when incorporating Excel data published by the government into websites, I would sometimes convert the data into JSON format and use JSON as a mock database instead of importing it into an actual database.

During these times, I used various methods like Google Apps Script in spreadsheets, writing local conversion scripts, or using SaaS tools, but there was no stable, consistent method.

When another opportunity arose to import Excel data as JSON data, my desire to unify the approach grew, and I decided to create JSON Bay as the tool I wanted to use.

Problems JSON Bay Solves and Its Advantages

Challenges with Existing Services

• Confusing operations for programmers: We provide a friendly UI that even non-engineers can use intuitively
• Outdated UI/UX: Simple and modern atmosphere
• Low transparency: No registration required and we don't collect JSON data (※This may not apply to features planned for future implementation)

Main Features

Currently Available Features

📝 JSON Formatting & Compression

• JSON FormatterFormat JSON for readability (Pretty Print)
• Adjust indentation, sort, validate
• JSON CompressMinimize JSON file size
• Remove unnecessary spaces and line breaks (Minify)

For compression, you can perform preprocessing (minify or NDJSON processing), convert to zip format, and compare the performance of various compression methods.

🔄 JSON Conversion Tools

• JSON ⇔ YAMLConvert between JSON and YAML formats
• Useful for config files and CI/CD definitions
• JSON ⇔ CSVConvert between JSON and CSV formats
• Support for editing and importing/exporting tabular data
• JSON ⇔ Excel (XLSX)Convert between JSON and Excel formats
• Useful for business documents and report creation
• JSON ⇔ StringConvert between JSON and strings
• Convenient for escape processing and code embedding

Features in Development

• We're planning a feature that allows JSON data to be used directly as API mocks. The data itself will be operable by users from a preview screen in any format (Excel-style, YAML-style, etc.), and I hope it will become like a read-focused database that's more convenient than SQLite.
• We're also considering MCP implementation. It's still in the conceptual stage, but if we can nicely call up each page's features from chat, I think we'll implement it. It depends on feasibility.
• We're considering, but not committed to, integrating with Supabase to store JSON data directly as a single table.
• We plan to implement other general JSON editing features. We also plan to gradually support large files.

Target Users and Use Cases

Primary Targets

• Non-engineer developers: As an alternative DB for handling simple data when database design barriers are too high
• API developers: Formatting and checking API responses
• Frontend engineers: Checking data structures and creating mock data
• Data analysts: Data processing through CSV/Excel ⇔ JSON conversion
• DevOps/SRE engineers: Converting between YAML config files and JSON

Specific Use Scenarios

• Checking and formatting response data during API development
• Converting between config files (JSON/YAML)
• Converting Excel data for input into JSON APIs
• Improving readability of log files and dump data
• Editing business data

Pricing & Plans

Completely Free - No Ads, No Charges

If we implement the mock API feature in the future, we're considering a usage-based plan only for that feature. Currently, JSON Bay is completely free to use.

Frequently Asked Questions (FAQ)

Q: Is JSON data sent to a server?

A: No. At the current stage, all processing is completed within the browser, and JSON data is never transmitted externally. This will only have exceptions if necessary for features we implement in the future.

Q: What data formats are supported?

A: We support JSON, YAML, CSV, Excel (XLSX), and string formats.

Q: Are there file size limitations?

A: There are no limits within the browser's memory constraints, but since we haven't yet optimized for large files, errors may occur depending on the environment.

Q: Can I use it on mobile devices?

A: You can use it, but since it's designed for laptops, issues may occur. If you contact us through inquiries, it will be easier to respond according to demand.

Developer's Thoughts - From Actual User Experience

I created JSON Bay because I wanted to use it myself as a developer. I aim to make it a truly user-friendly tool by immediately improving issues I notice while using it daily.

There are various ways to edit JSON, but my motivation for development is wanting to consolidate everything in one place. Beyond just editing, I want to expand functionality in various ways—like mock creation, database integration, and MCP implementation—to make it a tool I want to use even more.