离线 · 无上传 · 浏览器本地完成Offline · no uploads · runs in the browser
JSON 转纯文本——离线、逐行可读、不上传JSON to plain text offline, readable line by line, no upload
想要「能读的 JSON」但不想要 HTML 那层壳，这条路的产物就是一段纯文本。它是两步合成的：先把 JSON 渲染成可折叠的语法高亮查看器，再从那份页面里提取可读文字。实测一份三条记录的对象数组，拿到的是这样的形状——`[ Array(3){ Object(4)"name": "Alice",` 然后每个键各占一行、以 `},` 分隔、末尾收一个 `]`。也就是说：层级、数组与对象的**计数摘要**（`Array(3)`、`Object(4)`）会以文字留下来，字符串带引号、数字与布尔不带；而查看器里的缩进是 CSS 边距、颜色是样式，**都不会变成字符**。所以它适合贴进工单、聊天或纯文本笔记，不适合当成缩进良好的 JSON 副本——那份直接用原文件就好。Sometimes you want readable JSON without the HTML wrapper, and this route hands back plain text. It is two steps: the file is rendered as a collapsible, syntax-coloured viewer, and the readable text is then extracted out of that page. Measured on an array of three objects, the result starts `[ Array(3){ Object(4)"name": "Alice",`, each key lands on its own line, records are separated by `},` and the file closes with `]`. So the structure and the `Array(3)` / `Object(4)` count summaries survive as words, strings keep their quotes while numbers and booleans do not — and the viewer’s indentation is a CSS margin and its colours are styles, which means **neither becomes a character**. Good for a ticket, a chat message or a notes file; not a substitute for a nicely indented JSON copy, which is what the original already is.
这条链路怎么走How the route runs
JSONJSON HTMLHTML 纯文本 (TXT)plain text (TXT)
共 2 步，由扩展的路径搜索自动选出，中间产物不落盘。2 steps, chosen by the extension's own path search; intermediate results never touch the disk.
会保留什么What carries over
- 逐行结构：每个键值对占一行，对象之间以 `},` 分开，数组与对象的开头带着 `Array(n)` / `Object(n)` 的计数摘要Line by line: one key and value per line, records separated by `},`, and arrays and objects carry their `Array(n)` / `Object(n)` count at the opening
- 值按 JSON 类型呈现：字符串带引号，数字、布尔与 `null` 不带——所以 `30` 与 `"30"` 在文本里仍然分得开Values keep their JSON type in the text: strings are quoted while numbers, booleans and `null` are not, so `30` and `"30"` stay distinguishable
- 中文、emoji 与其他非 ASCII 字符按 UTF-8 原样保留，不会被转义成 `\uXXXX`Chinese text, emoji and other non-ASCII characters survive as UTF-8 and are not escaped into `\uXXXX`
- 提取只读文字：脚本、样式这些节点整段不进入结果，页面里指向网络的引用也从不被请求Only text is extracted: script and style nodes never enter the result, and nothing the page points at on the network is ever fetched
如实说明的限制What it does not do
- 没有缩进：查看器的层级是 CSS 边距与 `<details>` 折叠，不是空格或制表符，所以纯文本里只有换行表示层级No indentation: the viewer’s hierarchy is a CSS margin and `<details>` folding rather than spaces or tabs, so in plain text only line breaks mark depth
- 没有配色与折叠交互：颜色与「点开看」都随 HTML 一起消失，只剩结构与摘要文字No colour and no folding: the palette and the click-to-open behaviour leave with the HTML, and structure plus the count summaries are all that remains as words
- 键的顺序与源文件一致，但对象内的键不会被重排或补全——缺的键就是没有那一行Key order follows the source, but nothing is invented or reordered inside an object — a key a record lacks simply has no line
- 深层嵌套或超大文档会产出一段极长的文本：它是整份一次写出的，不做分页也不截断（要翻页就留在 HTML 那份）A deep or huge document yields a very long piece of text: it is written out whole, without pagination or truncation (stay on the HTML when you need to skim)
- 解析不了的 JSON 直接报错，不会给你一段半截文字；单个文件上限 100 MB、一批最多 200 个JSON that cannot be parsed fails instead of returning half a file; 100 MB per file and 200 files per batch
实操提示Working with it
- 要的是能对着屏幕读并顺手折叠：走 JSON 转 HTML，同一份内容、带配色与折叠，还能在浏览器里直接打印To read it on screen with folding and colour: take JSON to HTML — same content, plus the palette and click-to-open, printable straight from the browser
- 要的是能贴进表格或文档：JSON 转 CSV（对象数组按键取并集，缺的键留空）或转 WordTo paste it into a table or document: take JSON to CSV (an array of objects becomes columns from the union of keys, missing ones left empty) or to Word
- 只想取某个字段的值：本项目不做 JSONPath / jq 那类查询——转成 HTML 用浏览器搜索，或本地用命令行工具更合适To pull out one field’s value: this project does not do JSONPath or jq-style queries — search the HTML output in a browser, or use a command-line tool locally
常见问题Questions people actually ask
转出来的文本还是缩进良好的 JSON 吗？Is the result nicely indented JSON?
不是。产物是查看器那份内容的文字提取，层级靠换行与 `Array(n)` / `Object(n)` 摘要表达，而不是靠空格。要规整缩进的 JSON，直接用源文件（工作台可预览并编辑文本），或用命令行 `jq .`。No. The artefact is text extracted from the viewer, so depth shows as line breaks and `Array(n)` / `Object(n)` counts rather than as spaces. For indented JSON, use the source file (the workbench previews and lets you edit text) or `jq .` on the command line.
那行 `Object(4)` 是什么？会不会污染数据？What is that `Object(4)` — does it pollute the data?
它是查看器给每个对象与数组的计数摘要，随文字一起被提取出来（实测：`[ Array(3){ Object(4)"name": "Alice",`）。它是给人读的辅助信息，但如果你要把文本再喂回程序，请选 JSON 转 CSV 或直接保留 .json。It is the viewer’s count summary for each object and array, extracted along with the text (measured: `[ Array(3){ Object(4)"name": "Alice",`). It exists to be read by a person; if the text is going back into a program, take JSON to CSV or keep the .json instead.
含 token 或身份证号的 JSON 会离开这台电脑吗？Does JSON containing tokens or ID numbers ever leave this machine?
不会。解析、渲染、提取文字都在扩展自己的标签页里完成，只申请 storage 权限、没有 host 权限，产物里也没有把远端资源当代码执行的路径。No. Parsing, rendering and text extraction all happen inside the extension’s own tab: the storage permission only, no host permissions, and no path in the bundle that executes remotely hosted code.
不需要账号，也不需要联网：装好扩展后点图标，在新标签页里打开工作台，文件从磁盘直接选。No account and no network: install the extension, click its icon, and the workbench opens in a new tab reading straight off your disk.
从 Chrome 应用商店安装Install from the Chrome Web Store 安装步骤Install steps GitHub 源码Source on GitHub