Just the Fields
Launch GitHub

Browser-based. Offline-friendly. Zero setup.

See what matters in your JSON.

Just the Fields (JTF) is a lightweight JSON viewer that helps you focus on the fields that matter. Drop in files, browse safely, search across everything you loaded, and use templates to control what you see.

Launch JTF Browse templates Read the docs
Runs 100% in your browser No installs No uploads GitHub Pages friendly

Built for real-world JSON

API responses, Issue lists, RFIs, and big messy exports.

  • Records mode for structured payloads with templates.
  • Dataset mode for large arrays with filter and jump-to-row.
  • Safe rendering with collapsible objects and arrays.
  • Viewer search to find values in the active record (optionally inside collapsed sections).
  • Global search to find matches across all uploaded files, including Dataset rows.
Dataset mode showing a large JSON array (light theme)
Dataset mode showing a large JSON array

Features

Simple, focused, and fast. No feature bloat. No drama.

Records and dataset views

JTF adapts to common JSON shapes and lets you switch modes anytime.

Template-driven layout

Control what shows up and in what order using plain JSON template files.

Safe exploration

Expand objects and arrays only when you want to. Big stuff stays collapsed.

Search local or global

Use Viewer search to inspect the current record, or Global search to scan all uploaded files (including Dataset rows).

Dark mode

Easy on the eyes when you're hunting down that one weird value at 2am.

Works offline

Static files only. Host it anywhere. Run it locally. Use it on a plane.

Workflow

Four steps. No onboarding video required.

1

Drop in JSON

Drag and drop a JSON file, or pick one from your device.

2

Pick a view

Records mode for structured payloads, Dataset mode for large arrays.

3

Apply a template

Download a starter template, edit paths and labels, then upload it back.

4

Search and inspect

Use Global search to find where something lives, then Viewer search to inspect it in context.

Ready to try it?

Launch the app and drop in a JSON file. That’s it. That’s the whole setup.

Launch JTF View source

Templates

Templates are plain JSON files. They define layout only: what fields appear and in what order. Different export shapes (Plain vs Combined) require different templates.

Starter template

Download, edit in any text editor, upload back into JTF.

  • Define sections and fields using dot paths (like Status.Name).
  • Use chips for people, teams, and simple lists.
  • Render arrays as compact cards using format: "json" plus sub fields.
  • Missing fields are skipped, so templates are forgiving.
  • Optional match rules help templates apply only to the right records.
  • Plain and Combined exports have different shapes and usually need separate templates.
View templates Template guide

Auto (best match)

If you upload multiple templates, JTF can automatically pick the best one per record in Records mode.

  • Templates must match top-level record keys and hit real paths.
  • Best match is based on field hits, then match specificity.
  • If nothing fits, JTF falls back safely to the full record view.
  • For Combined exports, Auto works best with general templates (for example “Change Items – All types”).

Template guide

A practical, expandable guide to help you get templates working quickly. If you want the full reference, it still lives in the repo.

The mental model: two modes Templates apply in Records mode only

Dataset mode

Big flat arrays (table-like).

  • Templates do not apply.
  • Use the Dataset filter and Jump-to-row.

Records mode

Structured objects and API responses.

  • Templates control layout and field order.
  • Templates can also build the Record dropdown labels.

If your template “does nothing”, the first thing to check is your mode. Global search ignores mode and searches everything you uploaded.

Basic workflow Download → edit → upload → select
  1. In JTF, click Download in the Templates panel to get a starter template.
  2. Edit it (paths and labels) in any text editor (supports .json and .jsonc).
  3. Upload the template back into JTF.
  4. Select it in the Template dropdown.

If your browser opens the JSON instead of downloading it, use Save As and store it locally.

Template anatomy What’s inside the file
  • templateName
  • match (optional): controls when it applies
  • recordLabel (optional): controls Record dropdown labels
  • layout: ordered sections and fields

If a path does not exist, it is skipped. Nothing crashes.

Paths How JTF finds values

Paths are dot-separated, and can include array indexes:

Status.Name AssignedTo.Email Items[0].Title ViewerUrl

Practical tip: copy real property names from the Raw JSON view and build one field at a time.

Formats How values display
textDefault
badgeStatus pills
dateReadable date/time
linkClickable URLs
multilinePreserve line breaks
jsonNested object/array
chipsCompact badges
kvlistKey → value list

If the value is the wrong type for a format, the field is skipped.

Match rules Apply the right template to the right record
  • Match rules decide whether a template applies to a given record.
  • Match is not filtering, not a query language, and not a transform.
  • Keep match rules simple so templates stay predictable.

Tip: Plain and Combined exports use different data shapes and always require separate templates.

Record labels Make “Record 12” human

A template can build Record dropdown labels from multiple fields in order. If fields are missing, JTF falls back safely.

This is how “Record 12” becomes something like “#RFI-1042 Window detail (Open)”.

When a template matches but shows nothing The common “why is it blank?” checklist

Fix is usually one of:

  • Wrong mode (Dataset vs Records)
  • Wrong path (typo or different casing)
  • Template is for a different record shape

JTF shows a friendly hint card and still lets you view the full record.

Guardrails What templates cannot do
  • Declarative only (layout)
  • No scripting
  • No conditional logic
  • No data mutation

JTF reads data. It does not change data.

Templates For more details, view the formatted guide

Privacy first

Your data stays on your device. Always.

100% client-side processing

JTF runs entirely in your browser. No uploads, no backend, no accounts, no tracking. If your JSON is sensitive, good. Keep it that way.

Host it anywhere

It’s static files. GitHub Pages, internal servers, or a local folder with a tiny web server.

Offline-friendly

Once loaded, it works without internet. Ideal for job sites, flights, and cursed Wi‑Fi.

Docs and links

Everything you need, without sending you down a rabbit hole.

Launch JTF Open the live app. GitHub repo Source, issues, and releases. Templates guide How to create and use templates. Templates Examples you can download and edit.

JTF is open source and intentionally lightweight. If you want a feature, open an issue with a clear use case. If you want it tomorrow, bribe time itself.