Large Files
Large JSON files need a different interaction model than small examples. JSONFiddle protects the browser by blocking expensive views when a file would require rendering too many nested branches at once.
Current Behavior
| View | Large-file behavior |
|---|---|
| Graph | Pauses and recommends Grid or Query |
| Explorer | Pauses and recommends Grid or Query |
| Grid | Opens table-oriented sources and nested arrays |
| Query | Lets you extract targeted subsets |
| SQL | Lets you aggregate and filter without rendering every branch |
The guard exists because Graph and Explorer need to build a full structural tree. Multi-megabyte responses can contain tens of thousands of fields, and rendering all of them can make the browser sluggish.
Recommended Workflow
- Open the file.
- If Graph or Explorer is blocked, click Open Grid or Open Query.
- Use the Grid source selector to choose the object or array you want.
- Use column search and flattening only for the fields you need.
- Use Query or SQL to extract a smaller working subset.
- Open the subset in Graph or Explorer if you need a visual explanation.
Why Grid and Query Work Better
Grid can focus on a selected source such as payload.orderLineItems[] instead of rendering the entire JSON tree. Query and SQL can ask for a narrow result before any visual rendering happens.
Examples:
$.payload.orderLineItems[*].orderLineNumber
SELECT orderLineNumber, productName, netSalesPriceUSD
FROM order_line_items
WHERE netSalesPriceUSD > 0
ORDER BY netSalesPriceUSD DESC;
Paid Workspace Roadmap
Chunked large-file exploration is planned as a paid workspace feature. The intended direction is:
- Parse and index large payloads incrementally.
- Render only visible branches or rows.
- Keep search indexes separate from full visual rendering.
- Let Graph and Explorer load branches on demand.
- Preserve privacy controls around cloud save and share snapshots.
This is technically possible in JSONFiddle because the app already separates source files, workspace metadata, and view state. The current guard is a deliberate safety step until chunked rendering is production-ready.
What to Avoid
- Expanding every branch in a large nested object.
- Flattening hundreds of columns unless you need CSV export.
- Opening deeply nested objects inline inside wide Grid rows.
- Sharing production data without reviewing what the snapshot includes.