Open a local file and see its structure without leaving the source.
Visualize structured text
See the structure inside the source.
Treease turns JSON, YAML, TOML, CSV, and embedded payloads into a graph you can inspect, trace, edit, compare, and export with confidence.
Visual structure stays attached to the file.
Treease keeps source text, graph context, compare, and export preview attached to the same working document, so users can understand the structure before they act on it.
Trace fields across graph, tree path, and source text without losing place.
Review, convert, and export only after the structure looks right.
See, trace, and edit with context.
Treease is built for the repetitive work around structured files: opening them, seeing their shape, tracing exact fields, and making changes without losing the source.
Open a local file and see the real structure.
Load supported structured files directly into the editor and visualize their shape from the first step.
Clean up the current document in place.
Format, minify, or sort keys without leaving the editor or breaking visual context.
Lift the active JSON container out of mixed logs.
Put the cursor inside a JSONL row or embedded payload and let the graph isolate the active container from surrounding log noise.
Trace a field from graph to source.
Search the graph, land on the exact node, and keep tree path, highlight, and source reveal aligned.
Edit either side and keep both in sync.
Update a value in graph or source text and keep both views anchored to the same document state. Hover previews and local graph context stay nearby while you work.
Query, convert, and visualize from the CLI.
Use jq-style expressions for structured data work, then open a readonly local graph view when the result needs visual structure.
Query
treease '.services.api.url' example.jsonConvert
treease -o yaml '.' example.jsonVisualize
treease web '.services.api' example.jsonAct on structure once it is clear.
Treease keeps import progress, conversion preview, and compare decisions inside the same visual workflow, so users can verify structure before exporting or trusting a diff.
Keep large JSON imports transparent.
See visible progress while large JSON is parsed and rendered, instead of waiting on a blank screen.
Preview converted output before download.
Confirm the target format in the same workspace before the file leaves the browser.
Compare structure before you trust the diff.
Prefer structural comparison first. Fall back to text diff only when structure cannot be compared safely.
Pricing
A clearer way to work with structured data.
Start with the essential tools for understanding your files. Upgrade when your workflow needs more room to explore, compare, and ship.
ESSENTIALS
Free
Everything you need to make sense of a structured file.
$0 / month
Start free - Visualize structured documents
- Trace fields from graph to source
- Structural comparisons
- Share link validity: up to 7 days
- Bidirectional editing: up to 10 documents per month
- Large-file visualizations and processing: up to 3 runs per month
- AI features: not included
MOST POPULAR
Pro
More space for the documents and decisions in your day-to-day work.
$4.98 / month
- Visualize structured documents
- Trace fields from graph to source
- Structural comparisons
- Share link validity: up to 365 days
- Bidirectional editing: unlimited
- Large-file visualizations and processing: unlimited
- AI features: included usage
SAVE 20%
Pro yearly
The full Pro workflow with a lower effective monthly price.
$3.98 / month, billed annually
- Visualize structured documents
- Trace fields from graph to source
- Structural comparisons
- Share link validity: up to 365 days
- Bidirectional editing: unlimited
- Large-file visualizations and processing: unlimited
- AI features: included usage
FAQ
Treease works best when the page is explicit about what it does well, and what still belongs outside the graph view.
Why visualize structured text in Treease?
Because raw JSON, YAML, TOML, CSV, or embedded payloads get hard to follow long before they become hard to edit. Treease turns source text into a graph so users can see the structure first, then trace, edit, compare, and export with context.
What kinds of files and workflows does Treease cover?
Treease supports local import, format and minify commands, key sorting, active-container isolation inside mixed logs, graph search with tree path reveal, local value preview, synchronized text and graph edits, structural compare with text fallback, export preview, and visible progress for large JSON imports.
What makes Treease different from a plain editor or JSON viewer?
Treease keeps source text and graph context attached to the same document state. Instead of showing a disconnected preview, it lets users move from text to graph to tree path to output while staying anchored to the same file.
When should I use Treease instead of a terminal tool or general editor?
Use Treease when seeing the structure matters: inspecting nested data, tracing fields, checking changes, or previewing converted output. General-purpose editing, custom CLI filters, and batch automation still belong in an editor or terminal when the job stops being document-centric.
Try it with a real file.
Open a real document, see the structure, and keep every next step anchored to what you already understand.