[{"data":1,"prerenderedAt":964},["ShallowReactive",2],{"blog-post-/blog/zh-cn/how-to-format-json-online":3,"related-posts-/zh-CN/blog/how-to-format-json-online":257},{"id":4,"title":5,"author":6,"body":7,"category":240,"date":241,"description":242,"extension":243,"featured":244,"image":245,"meta":246,"navigation":247,"path":248,"readingTime":249,"seo":250,"stem":251,"tags":252,"tools":255,"__hash__":256},"content/blog/zh-CN/how-to-format-json-online.md","如何在 2026 年在线格式化 JSON","Anything Tools Editorial",{"type":8,"value":9,"toc":228},"minimark",[10,14,18,27,32,35,54,62,65,68,95,103,106,123,126,129,132,149,156,160,163,177,180,183,186,194,198,215,218],[11,12,5],"h1",{"id":13},"如何在-2026-年在线格式化-json",[15,16,17],"p",{},"杂乱的 JSON 会明显拖慢排查效率。少一个逗号、错一个引号，或者嵌套层级太深，都会让一次本来几分钟能完成的检查变成低效体力活。好用的在线 JSON 格式化工具，核心价值不是“排版好看”，而是让你更快看懂数据结构，并及时发现语法问题。",[15,19,20,21,26],{},"如果你想直接开始，可以使用 ",[22,23,25],"a",{"href":24},"/dev/json-formatter","Anything Tools JSON Formatter","。它适合在浏览器里快速粘贴原始 JSON、整理结构并检查内容。",[28,29,31],"h2",{"id":30},"什么时候需要在线-json-格式化工具","什么时候需要在线 JSON 格式化工具",[15,33,34],{},"JSON 格式化不只是后端开发者才需要。下面这些场景都很常见：",[36,37,38,42,45,48,51],"ul",{},[39,40,41],"li",{},"查看 webhook 回调数据",[39,43,44],{},"阅读导出的配置文件",[39,46,47],{},"整理复制出来的 API 响应",[39,49,50],{},"发布前检查配置片段是否合法",[39,52,53],{},"给同事或文档准备更易读的示例",[15,55,56,57,61],{},"本质上，它解决的是",[58,59,60],"strong",{},"可读性","问题。缩进一旦清晰，数组、对象、布尔值和 null 的层级关系就会更容易判断。",[28,63,64],{"id":64},"一个好工具应该具备什么",[15,66,67],{},"实用的 JSON Formatter 不应只会“加空格”。更重要的是：",[69,70,71,77,83,89],"ol",{},[39,72,73,76],{},[58,74,75],{},"格式化输出清晰","，方便快速浏览嵌套结构。",[39,78,79,82],{},[58,80,81],{},"能提示语法错误","，而不是让你盲猜哪里写坏了。",[39,84,85,88],{},[58,86,87],{},"交互足够快","，方便你一边修一边试。",[39,90,91,94],{},[58,92,93],{},"结果易于复制","，可直接放回代码、工单或文档里。",[15,96,97,98,102],{},"如果你还需要处理 URL 中的参数编码，配合 ",[22,99,101],{"href":100},"/dev/url-encode","URL Encoder"," 一起使用也很顺手。",[28,104,105],{"id":105},"推荐的实际流程",[69,107,108,111,114,117,120],{},[39,109,110],{},"先把原始 JSON 粘贴进去。",[39,112,113],{},"先执行格式化。",[39,115,116],{},"如果报错，就重点查看出错行附近。",[39,118,119],{},"修正常见问题，例如多余逗号、单引号、缺少括号。",[39,121,122],{},"再把整理好的结果复制回你的项目或测试环境。",[15,124,125],{},"这个流程通常比直接在日志里硬看一长串压缩 JSON 高效得多。",[28,127,128],{"id":128},"常见错误有哪些",[15,130,131],{},"最常见的几类问题几乎每次都会出现：",[36,133,134,137,140,143,146],{},[39,135,136],{},"用了单引号而不是双引号",[39,138,139],{},"结尾多写了逗号",[39,141,142],{},"漏掉右花括号或右方括号",[39,144,145],{},"把数字和字符串混用",[39,147,148],{},"粘贴进来的是 JavaScript 对象，而不是严格 JSON",[15,150,151,152,155],{},"要记住：",[58,153,154],{},"JSON 比普通 JavaScript 对象更严格","。格式化工具如果拒绝输入，通常说明这段内容还不是合法 JSON。",[28,157,159],{"id":158},"格式化和校验并不完全一样","“格式化”和“校验”并不完全一样",[15,161,162],{},"这两个动作经常一起出现，但不等价：",[36,164,165,171],{},[39,166,167,170],{},[58,168,169],{},"格式化","：让合法 JSON 更易读。",[39,172,173,176],{},[58,174,175],{},"校验","：判断 JSON 语法是否真的正确。",[15,178,179],{},"一个合格的工具最好同时覆盖这两件事。只做美化、不做校验，实际价值会打折。",[28,181,182],{"id":182},"浏览器工作流与隐私",[15,184,185],{},"很多 JSON 里会包含内部 ID、客户字段或业务元数据，所以越轻量的处理方式越好。浏览器里的工具能降低切换成本，也更适合临时检查和快速调试。",[15,187,188,189,193],{},"如果你还经常需要统计日志、提示词或文本字段长度，可以顺手使用 ",[22,190,192],{"href":191},"/text/text-counter","Text Counter","。",[28,195,197],{"id":196},"_2026-年的实践建议","2026 年的实践建议",[36,199,200,203,206,209,212],{},[39,201,202],{},"比较两个版本前先格式化",[39,204,205],{},"对外分享示例时尽量保留最小必要字段",[39,207,208],{},"配置文件提交前先做一次校验",[39,210,211],{},"不要手工编辑大段压缩 JSON",[39,213,214],{},"在文档里保留一份干净、规范的样例",[28,216,217],{"id":217},"结论",[15,219,220,221,224,225,227],{},"在线格式化 JSON 到今天依然是高频且实用的开发动作。真正节省时间的，不是“排版更整齐”，而是",[58,222,223],{},"更快理解结构、更少犯错","。如果你需要一个轻量直接的浏览器流程，就从 ",[22,226,25],{"href":24}," 开始。",{"title":229,"searchDepth":230,"depth":230,"links":231},"",2,[232,233,234,235,236,237,238,239],{"id":30,"depth":230,"text":31},{"id":64,"depth":230,"text":64},{"id":105,"depth":230,"text":105},{"id":128,"depth":230,"text":128},{"id":158,"depth":230,"text":159},{"id":182,"depth":230,"text":182},{"id":196,"depth":230,"text":197},{"id":217,"depth":230,"text":217},"开发者工具","2026-03-24T00:00:00.000Z","一篇实用指南，教你如何在线格式化、校验并清理 JSON，无需安装额外软件。","md",false,"/blog/how-to-format-json-online.png",{},true,"/blog/zh-cn/how-to-format-json-online",null,{"title":5,"description":242},"blog/zh-CN/how-to-format-json-online",[253,240,254],"JSON 格式化","数据处理",[24],"Jcxs3Ev_q5z7umKRMTgST_m_laRClvDZ6_-dvyUamuw",[258,669],{"id":259,"title":260,"author":6,"body":261,"category":240,"date":657,"description":658,"extension":243,"featured":244,"image":659,"meta":660,"navigation":247,"path":661,"readingTime":441,"seo":662,"stem":663,"tags":664,"tools":667,"__hash__":668},"content/blog/zh-CN/how-to-convert-csv-to-json-online.md","如何在 2026 年在线将 CSV 转成 JSON",{"type":8,"value":262,"toc":647},[263,266,269,277,281,284,287,304,307,310,313,316,344,347,514,517,521,524,527,544,547,550,567,570,573,576,579,582,596,602,605,608,614,618,635,637,643],[11,264,260],{"id":265},"如何在-2026-年在线将-csv-转成-json",[15,267,268],{},"CSV 仍然无处不在。它经常出现在表格导出、分析工具、CRM、支付系统以及内部后台中。真正麻烦的时刻，是你需要把这种扁平表格变成可供 API、脚本或应用使用的结构化数据。",[15,270,271,272,276],{},"如果你想要最快的浏览器流程，可以直接使用 ",[22,273,275],{"href":274},"/dev/csv-to-json","Anything Tools CSV 转 JSON 工具","。你可以粘贴 CSV、转换成 JSON，然后直接复制结果，不需要安装额外软件。",[28,278,280],{"id":279},"什么时候适合把-csv-转成-json","什么时候适合把 CSV 转成 JSON",[15,282,283],{},"当表格型数据需要进入更适合开发处理的格式时，这种转换就很有价值。",[15,285,286],{},"常见场景包括：",[36,288,289,292,295,298,301],{},[39,290,291],{},"把表格导出导入到 Web 应用",[39,293,294],{},"把市场或销售导出数据整理成 API payload",[39,296,297],{},"准备测试用示例数据",[39,299,300],{},"在写脚本前先清理简单数据集",[39,302,303],{},"在把后台数据交给工程团队前先做结构转换",[15,305,306],{},"CSV 对人类来说容易打开，JSON 对软件来说通常更容易处理。",[28,308,309],{"id":309},"转换过程中到底发生了什么",[15,311,312],{},"CSV 会把每一行保存成一条记录，把每一列保存成一个分隔值。JSON 则会给你明确的键名、数组和更清晰的数据结构。",[15,314,315],{},"比如下面这段 CSV：",[317,318,322],"pre",{"className":319,"code":320,"language":321,"meta":229,"style":229},"language-csv shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","name,email,plan\nAva,ava@example.com,pro\nLeo,leo@example.com,starter\n","csv",[323,324,325,333,338],"code",{"__ignoreMap":229},[326,327,330],"span",{"class":328,"line":329},"line",1,[326,331,332],{},"name,email,plan\n",[326,334,335],{"class":328,"line":230},[326,336,337],{},"Ava,ava@example.com,pro\n",[326,339,341],{"class":328,"line":340},3,[326,342,343],{},"Leo,leo@example.com,starter\n",[15,345,346],{},"通常会变成这样的 JSON：",[317,348,352],{"className":349,"code":350,"language":351,"meta":229,"style":229},"language-json shiki shiki-themes material-theme-lighter material-theme material-theme-palenight","[\n  {\n    \"name\": \"Ava\",\n    \"email\": \"ava@example.com\",\n    \"plan\": \"pro\"\n  },\n  {\n    \"name\": \"Leo\",\n    \"email\": \"leo@example.com\",\n    \"plan\": \"starter\"\n  }\n]\n","json",[323,353,354,360,365,392,413,433,439,444,464,484,502,508],{"__ignoreMap":229},[326,355,356],{"class":328,"line":329},[326,357,359],{"class":358},"sMK4o","[\n",[326,361,362],{"class":328,"line":230},[326,363,364],{"class":358},"  {\n",[326,366,367,370,374,377,380,383,387,389],{"class":328,"line":340},[326,368,369],{"class":358},"    \"",[326,371,373],{"class":372},"spNyl","name",[326,375,376],{"class":358},"\"",[326,378,379],{"class":358},":",[326,381,382],{"class":358}," \"",[326,384,386],{"class":385},"sfazB","Ava",[326,388,376],{"class":358},[326,390,391],{"class":358},",\n",[326,393,395,397,400,402,404,406,409,411],{"class":328,"line":394},4,[326,396,369],{"class":358},[326,398,399],{"class":372},"email",[326,401,376],{"class":358},[326,403,379],{"class":358},[326,405,382],{"class":358},[326,407,408],{"class":385},"ava@example.com",[326,410,376],{"class":358},[326,412,391],{"class":358},[326,414,416,418,421,423,425,427,430],{"class":328,"line":415},5,[326,417,369],{"class":358},[326,419,420],{"class":372},"plan",[326,422,376],{"class":358},[326,424,379],{"class":358},[326,426,382],{"class":358},[326,428,429],{"class":385},"pro",[326,431,432],{"class":358},"\"\n",[326,434,436],{"class":328,"line":435},6,[326,437,438],{"class":358},"  },\n",[326,440,442],{"class":328,"line":441},7,[326,443,364],{"class":358},[326,445,447,449,451,453,455,457,460,462],{"class":328,"line":446},8,[326,448,369],{"class":358},[326,450,373],{"class":372},[326,452,376],{"class":358},[326,454,379],{"class":358},[326,456,382],{"class":358},[326,458,459],{"class":385},"Leo",[326,461,376],{"class":358},[326,463,391],{"class":358},[326,465,467,469,471,473,475,477,480,482],{"class":328,"line":466},9,[326,468,369],{"class":358},[326,470,399],{"class":372},[326,472,376],{"class":358},[326,474,379],{"class":358},[326,476,382],{"class":358},[326,478,479],{"class":385},"leo@example.com",[326,481,376],{"class":358},[326,483,391],{"class":358},[326,485,487,489,491,493,495,497,500],{"class":328,"line":486},10,[326,488,369],{"class":358},[326,490,420],{"class":372},[326,492,376],{"class":358},[326,494,379],{"class":358},[326,496,382],{"class":358},[326,498,499],{"class":385},"starter",[326,501,432],{"class":358},[326,503,505],{"class":328,"line":504},11,[326,506,507],{"class":358},"  }\n",[326,509,511],{"class":328,"line":510},12,[326,512,513],{"class":358},"]\n",[15,515,516],{},"这种结构更适合在 JavaScript、API 请求和测试数据中复用。",[28,518,520],{"id":519},"csv-最常见的问题","CSV 最常见的问题",[15,522,523],{},"转换本身并不复杂，真正容易出问题的往往是输入数据。",[15,525,526],{},"典型问题包括：",[36,528,529,532,535,538,541],{},[39,530,531],{},"表头缺失或重复",[39,533,534],{},"分隔符不一致，比如逗号和分号混用",[39,536,537],{},"带引号字段里本身包含逗号",[39,539,540],{},"文件结尾有空行",[39,542,543],{},"某些数字看起来像数字，但其实应该保留为字符串",[15,545,546],{},"一个好的在线转换工具，能让你在数据进入后续系统之前先发现这些问题。",[28,548,549],{"id":549},"一套实用流程",[69,551,552,555,558,561,564],{},[39,553,554],{},"把原始 CSV 粘贴进转换工具。",[39,556,557],{},"确认分隔符和表头行识别正确。",[39,559,560],{},"先预览几行结果。",[39,562,563],{},"检查 ID、邮编、电话号码或 SKU 是否应该保留为字符串。",[39,565,566],{},"复制 JSON 输出，并在正式使用前做一次校验。",[15,568,569],{},"这一轮快速检查，通常就能避免大多数错误导入。",[28,571,572],{"id":572},"表头比很多人想象得更重要",[15,574,575],{},"表头质量，直接决定 JSON 质量。",[15,577,578],{},"如果 CSV 表头写得清楚，JSON 键名通常也会更干净；如果表头含糊或不一致，结果很快就会变得难用。",[15,580,581],{},"好的表头应该：",[36,583,584,587,590,593],{},[39,585,586],{},"唯一",[39,588,589],{},"有描述性",[39,591,592],{},"在不同导出之间保持稳定",[39,594,595],{},"没有意外空格",[15,597,598,599,601],{},"如果你想在转换后再快速整理一遍结果，可以接着使用 ",[22,600,25],{"href":24}," 提升可读性并做结构校验。",[28,603,604],{"id":604},"隐私与浏览器内转换",[15,606,607],{},"很多 CSV 文件都包含客户信息、运营导出或内部报表数据。这也是浏览器工具仍然有价值的原因之一：它减少了流程摩擦，让快速转换更容易掌控。",[15,609,610,611,613],{},"如果你还需要顺手检查 payload 大小、字段长度或导入备注，可以搭配 ",[22,612,192],{"href":191}," 一起使用。",[28,615,617],{"id":616},"_2026-年最佳实践","2026 年最佳实践",[36,619,620,623,626,629,632],{},[39,621,622],{},"转换前先清理表头",[39,624,625],{},"抽查开头和结尾几行",[39,627,628],{},"格式敏感的标识符尽量保留为字符串",[39,630,631],{},"发给 API 前先验证最终 JSON",[39,633,634],{},"保留一个小型样例文件用于重复测试",[28,636,217],{"id":217},[15,638,639,640,642],{},"在线把 CSV 转成 JSON 并不难，但输入是否干净仍然决定结果质量。真正的目标不只是换一种文件格式，而是得到可以放心使用的结构化数据。如果你想要快速的浏览器流程，可以从 ",[22,641,275],{"href":274}," 开始，把表格导出在几秒内变成可用 JSON。",[644,645,646],"style",{},"html .light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html.light .shiki span {color: var(--shiki-light);background: var(--shiki-light-bg);font-style: var(--shiki-light-font-style);font-weight: var(--shiki-light-font-weight);text-decoration: var(--shiki-light-text-decoration);}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html.dark .shiki span {color: var(--shiki-dark);background: var(--shiki-dark-bg);font-style: var(--shiki-dark-font-style);font-weight: var(--shiki-dark-font-weight);text-decoration: var(--shiki-dark-text-decoration);}html pre.shiki code .sMK4o, html code.shiki .sMK4o{--shiki-light:#39ADB5;--shiki-default:#89DDFF;--shiki-dark:#89DDFF}html pre.shiki code .spNyl, html code.shiki .spNyl{--shiki-light:#9C3EDA;--shiki-default:#C792EA;--shiki-dark:#C792EA}html pre.shiki code .sfazB, html code.shiki .sfazB{--shiki-light:#91B859;--shiki-default:#C3E88D;--shiki-dark:#C3E88D}",{"title":229,"searchDepth":230,"depth":230,"links":648},[649,650,651,652,653,654,655,656],{"id":279,"depth":230,"text":280},{"id":309,"depth":230,"text":309},{"id":519,"depth":230,"text":520},{"id":549,"depth":230,"text":549},{"id":572,"depth":230,"text":572},{"id":604,"depth":230,"text":604},{"id":616,"depth":230,"text":617},{"id":217,"depth":230,"text":217},"2026-04-01T00:00:00.000Z","一份实用指南，帮助你在浏览器中把 CSV 转成干净的 JSON，并减少表头与数据结构错误。","/blog/how-to-convert-csv-to-json-online.png",{},"/blog/zh-cn/how-to-convert-csv-to-json-online",{"title":260,"description":658},"blog/zh-CN/how-to-convert-csv-to-json-online",[665,240,666],"CSV 转 JSON","数据转换",[274],"di5kDnVjoe6Nanm8cu7XIQm8p5bjiSajOtCVWD1_6D8",{"id":670,"title":671,"author":672,"body":673,"category":240,"date":950,"description":951,"extension":243,"featured":244,"image":952,"meta":953,"navigation":247,"path":954,"readingTime":446,"seo":955,"stem":956,"tags":957,"tools":962,"__hash__":963},"content/blog/zh-CN/how-to-convert-unix-timestamp-to-date.md","如何在 2026 年把 Unix 时间戳转换为日期","Anything Tools Team",{"type":8,"value":674,"toc":939},[675,678,681,688,692,699,702,715,718,732,735,738,741,755,758,762,765,770,784,787,791,794,797,811,814,817,828,831,834,837,854,860,863,866,874,877,880,883,886,900,903,906,909,926,929,931,934],[11,676,671],{"id":677},"如何在-2026-年把-unix-时间戳转换为日期",[15,679,680],{},"Unix 时间戳几乎到处都在出现：API 返回、日志、数据库记录、分析事件、缓存键、定时任务。对系统来说它紧凑又高效，但对人类排查问题时并不直观。",[15,682,683,684,193],{},"这也是为什么开发者总要把一串原始数字转换成真正可读的日期和时间。如果你想用最快的方式处理这件事，可以直接打开 ",[22,685,687],{"href":686},"/dev/timestamp","Anything Tools Unix Timestamp Converter",[28,689,691],{"id":690},"unix-时间戳到底表示什么","Unix 时间戳到底表示什么",[15,693,694,695,698],{},"Unix 时间戳表示从 ",[58,696,697],{},"1970 年 1 月 1 日 00:00:00 UTC"," 到某一时刻所经过的秒数或毫秒数。",[15,700,701],{},"真正最容易出错的地方只有两个：",[36,703,704,710],{},[39,705,706,707],{},"有些系统用 ",[58,708,709],{},"秒",[39,711,706,712],{},[58,713,714],{},"毫秒",[15,716,717],{},"例如：",[36,719,720,726],{},[39,721,722,725],{},[323,723,724],{},"1711718400"," 通常是秒",[39,727,728,731],{},[323,729,730],{},"1711718400000"," 通常是毫秒",[15,733,734],{},"如果单位看错，转换出来的日期通常会离谱到一眼就知道不对。",[28,736,737],{"id":737},"为什么时间戳转换总是容易出错",[15,739,740],{},"多数时间戳问题并不是计算公式错了，而是上下文缺失：",[36,742,743,746,749,752],{},[39,744,745],{},"后端返回毫秒，前端却按秒处理",[39,747,748],{},"日志里是 UTC，浏览器展示的是本地时间",[39,750,751],{},"字符串值被错误解析",[39,753,754],{},"同一个排查流程里混用了 ISO 字符串、本地时间和 epoch 数字",[15,756,757],{},"因此调试时间字段时，先确认单位、时区和展示格式，再判断数据本身有没有问题。",[28,759,761],{"id":760},"用浏览器转换通常比临时写代码更快","用浏览器转换，通常比临时写代码更快",[15,763,764],{},"在日常开发里，每次都为一个时间戳去开控制台写一段临时代码，其实很低效。浏览器里的转换工具更适合快速排查。",[15,766,767,769],{},[22,768,687],{"href":686}," 的价值就在于它能让你：",[36,771,772,775,778,781],{},[39,773,774],{},"立即把时间戳转换为可读日期",[39,776,777],{},"把日期再转回 epoch",[39,779,780],{},"在秒与毫秒之间快速切换",[39,782,783],{},"不必把值发到别处就能直接查看结果",[15,785,786],{},"处理生产日志、Webhook 负载或复制出来的 JSON 片段时，这种工作流尤其顺手。",[28,788,790],{"id":789},"先分清-utc本地时间和-iso-字符串","先分清 UTC、本地时间和 ISO 字符串",[15,792,793],{},"时间戳本身并没有“时区偏见”。真正让人困惑的是展示方式。",[15,795,796],{},"同一个时间点，常见会被渲染成：",[36,798,799,802,805,808],{},[39,800,801],{},"UTC 时间",[39,803,804],{},"浏览器所在时区的本地时间",[39,806,807],{},"ISO 8601 字符串",[39,809,810],{},"应用内部自定义格式",[15,812,813],{},"它们指向的是同一个时刻，只是呈现方式不同。",[15,815,816],{},"当你觉得时间“不对”时，最有效的检查顺序通常是：",[69,818,819,822,825],{},[39,820,821],{},"原始时间戳对不对？",[39,823,824],{},"单位是秒还是毫秒？",[39,826,827],{},"你看到的是 UTC 还是本地时间？",[15,829,830],{},"这三步能解决大多数排查问题。",[28,832,833],{"id":833},"常见开发场景",[15,835,836],{},"时间戳转换经常出现在这些任务里：",[36,838,839,842,845,848,851],{},[39,840,841],{},"检查 token 什么时候过期",[39,843,844],{},"阅读审计日志",[39,846,847],{},"排查定时任务执行时间",[39,849,850],{},"校验分析事件是否延迟",[39,852,853],{},"对照数据库记录与 API 输出",[15,855,856,857,859],{},"如果时间戳只是一个更大 JSON 对象中的字段，也可以先用 ",[22,858,25],{"href":24}," 把结构整理清楚，再看日期字段会更省时间。",[28,861,862],{"id":862},"秒和毫秒的最快判断方法",[15,864,865],{},"如果你只记住一条经验规则，那就是先看位数：",[36,867,868,871],{},[39,869,870],{},"10 位数字通常是秒",[39,872,873],{},"13 位数字通常是毫秒",[15,875,876],{},"这不是数学定律，但在实际排查中非常有效，能快速挡掉大量低级错误。",[15,878,879],{},"另外也要警惕某些 API 文档写的是一种单位，实际通过中间层或 SDK 返回的却是另一种单位。",[28,881,882],{"id":882},"这些边界情况也别忽略",[15,884,885],{},"到了 2026 年，下面这些问题仍然值得留意：",[36,887,888,891,894,897],{},[39,889,890],{},"1970 年之前的负时间戳",[39,892,893],{},"老旧 32 位环境里的 2038 问题",[39,895,896],{},"夏令时切换导致的本地显示变化",[39,898,899],{},"JSON 中字符串和数字类型混用",[15,901,902],{},"现代浏览器和主流语言通常都能很好处理这些情况，但前提是你排查时足够明确。",[28,904,905],{"id":905},"一套可重复使用的排查流程",[15,907,908],{},"当某个时间值看起来可疑时，可以直接按这套流程走：",[69,910,911,914,917,920,923],{},[39,912,913],{},"复制原始时间戳。",[39,915,916],{},"先判断它是 10 位还是 13 位。",[39,918,919],{},"在浏览器里转换。",[39,921,922],{},"对比 UTC 和本地时间。",[39,924,925],{},"回溯这个字段来自哪个系统。",[15,927,928],{},"这样可以避免一种很常见的误区：表面上修的是展示 bug，实际上真正的问题是上游单位传错了。",[28,930,217],{"id":217},[15,932,933],{},"Unix 时间戳对机器很高效，但对人类并不友好。真正高效的做法，不是每次临时写脚本，而是手边一直有一套稳定的转换流程，并且先确认单位。",[15,935,936,937,227],{},"如果你需要一个轻量直接的方式来查看 epoch、互转日期，并快速区分秒和毫秒，可以从 ",[22,938,687],{"href":686},{"title":229,"searchDepth":230,"depth":230,"links":940},[941,942,943,944,945,946,947,948,949],{"id":690,"depth":230,"text":691},{"id":737,"depth":230,"text":737},{"id":760,"depth":230,"text":761},{"id":789,"depth":230,"text":790},{"id":833,"depth":230,"text":833},{"id":862,"depth":230,"text":862},{"id":882,"depth":230,"text":882},{"id":905,"depth":230,"text":905},{"id":217,"depth":230,"text":217},"2026-03-29T00:00:00.000Z","学习如何把 Unix 时间戳转换成人类可读日期，避开秒与毫秒混淆，并更高效地排查时间字段问题。","/blog/how-to-convert-unix-timestamp-to-date.png",{},"/blog/zh-cn/how-to-convert-unix-timestamp-to-date",{"title":671,"description":951},"blog/zh-CN/how-to-convert-unix-timestamp-to-date",[958,959,960,961,240],"Unix 时间戳","Epoch 时间","日期转换","调试",[686],"KJJ5-xphStiQykU_6qywEmVTjmHtsRT4YgDv6UGWGEg",1781140599389]