WebToSparkWhat is JSON?
JSON stands for JavaScript Object Notation. It is a text data format used to exchange structured values; it is not a program you need to execute. Objects use named members, arrays hold ordered values, and values can include strings, numbers, booleans and null.
A .json file can be opened in a text editor. It does not need to be uploaded to an online viewer. Prefer a local editor for research files containing sensitive source material. Large files may require an editor designed for their size.
How to open a JSON file
The same .json extension is used by many applications with different schemas. These field names describe WebToSpark, not a universal JSON document structure.
- Keep the original export. Use your operating system’s Open With command and choose a plain-text editor. An editor with JSON formatting and folding makes nested content easier to inspect.
- Confirm that you are reading the exported document rather than expecting a rendered web page. Inspect schemaVersion and source, then the content collections.
- For a single WebToSpark export, inspect primary, items and comments where present. For a multi-document export, inspect documents inside the batch envelope.
- Follow replies to inspect nested comments. Missing or empty fields can reflect unavailable page data; compare with the source and extraction warnings before drawing conclusions.
Which WebToSpark fields should I inspect?
JSON preserves the captured structure; it does not guarantee a complete discussion. Ordinary export does not fetch hidden replies, deleted comments or additional pages. Images and videos remain URL references.
| Field | What it describes |
|---|---|
| schemaVersion | The export schema version, not the extension release number. |
| source | Source page context such as URL and title. |
| primary / items | The main record and extracted list records, depending on page type. |
| comments / replies | Captured comment records and nested replies. |
| documents | Multiple documents inside a batch envelope. |
| extraction | Capture metadata and extraction warnings. |
JSON vs CSV and conversion limits
Choose CSV if your next step is filtering flat rows in Excel. Keep JSON when nesting or programmatic processing matters. A separate JSON-to-CSV conversion requires a mapping for nested arrays; changing a file extension is not conversion. WebToSpark does not accept arbitrary JSON uploads for conversion.
When the same captured source is available, request an additional export format through the extension. Plain files do not run the experimental Research Agent, and opening JSON does not call an AI service.