[{"data":1,"prerenderedAt":321},["ShallowReactive",2],{"tool-related-posts-/zh-CN/dev/timestamp-zh-cn":3},[4],{"id":5,"title":6,"author":7,"body":8,"category":302,"date":303,"description":304,"extension":305,"featured":306,"image":307,"meta":308,"navigation":309,"path":310,"readingTime":311,"seo":312,"stem":313,"tags":314,"tools":319,"__hash__":320},"content/blog/zh-CN/how-to-convert-unix-timestamp-to-date.md","如何在 2026 年把 Unix 时间戳转换为日期","Anything Tools Team",{"type":9,"value":10,"toc":289},"minimark",[11,15,19,28,33,41,44,59,62,77,80,83,86,100,103,107,110,115,129,132,136,139,142,156,159,162,174,177,180,183,200,208,211,214,222,225,228,231,234,248,251,254,257,274,277,280,283],[12,13,6],"h1",{"id":14},"如何在-2026-年把-unix-时间戳转换为日期",[16,17,18],"p",{},"Unix 时间戳几乎到处都在出现：API 返回、日志、数据库记录、分析事件、缓存键、定时任务。对系统来说它紧凑又高效，但对人类排查问题时并不直观。",[16,20,21,22,27],{},"这也是为什么开发者总要把一串原始数字转换成真正可读的日期和时间。如果你想用最快的方式处理这件事，可以直接打开 ",[23,24,26],"a",{"href":25},"/dev/timestamp","Anything Tools Unix Timestamp Converter","。",[29,30,32],"h2",{"id":31},"unix-时间戳到底表示什么","Unix 时间戳到底表示什么",[16,34,35,36,40],{},"Unix 时间戳表示从 ",[37,38,39],"strong",{},"1970 年 1 月 1 日 00:00:00 UTC"," 到某一时刻所经过的秒数或毫秒数。",[16,42,43],{},"真正最容易出错的地方只有两个：",[45,46,47,54],"ul",{},[48,49,50,51],"li",{},"有些系统用 ",[37,52,53],{},"秒",[48,55,50,56],{},[37,57,58],{},"毫秒",[16,60,61],{},"例如：",[45,63,64,71],{},[48,65,66,70],{},[67,68,69],"code",{},"1711718400"," 通常是秒",[48,72,73,76],{},[67,74,75],{},"1711718400000"," 通常是毫秒",[16,78,79],{},"如果单位看错，转换出来的日期通常会离谱到一眼就知道不对。",[29,81,82],{"id":82},"为什么时间戳转换总是容易出错",[16,84,85],{},"多数时间戳问题并不是计算公式错了，而是上下文缺失：",[45,87,88,91,94,97],{},[48,89,90],{},"后端返回毫秒，前端却按秒处理",[48,92,93],{},"日志里是 UTC，浏览器展示的是本地时间",[48,95,96],{},"字符串值被错误解析",[48,98,99],{},"同一个排查流程里混用了 ISO 字符串、本地时间和 epoch 数字",[16,101,102],{},"因此调试时间字段时，先确认单位、时区和展示格式，再判断数据本身有没有问题。",[29,104,106],{"id":105},"用浏览器转换通常比临时写代码更快","用浏览器转换，通常比临时写代码更快",[16,108,109],{},"在日常开发里，每次都为一个时间戳去开控制台写一段临时代码，其实很低效。浏览器里的转换工具更适合快速排查。",[16,111,112,114],{},[23,113,26],{"href":25}," 的价值就在于它能让你：",[45,116,117,120,123,126],{},[48,118,119],{},"立即把时间戳转换为可读日期",[48,121,122],{},"把日期再转回 epoch",[48,124,125],{},"在秒与毫秒之间快速切换",[48,127,128],{},"不必把值发到别处就能直接查看结果",[16,130,131],{},"处理生产日志、Webhook 负载或复制出来的 JSON 片段时，这种工作流尤其顺手。",[29,133,135],{"id":134},"先分清-utc本地时间和-iso-字符串","先分清 UTC、本地时间和 ISO 字符串",[16,137,138],{},"时间戳本身并没有“时区偏见”。真正让人困惑的是展示方式。",[16,140,141],{},"同一个时间点，常见会被渲染成：",[45,143,144,147,150,153],{},[48,145,146],{},"UTC 时间",[48,148,149],{},"浏览器所在时区的本地时间",[48,151,152],{},"ISO 8601 字符串",[48,154,155],{},"应用内部自定义格式",[16,157,158],{},"它们指向的是同一个时刻，只是呈现方式不同。",[16,160,161],{},"当你觉得时间“不对”时，最有效的检查顺序通常是：",[163,164,165,168,171],"ol",{},[48,166,167],{},"原始时间戳对不对？",[48,169,170],{},"单位是秒还是毫秒？",[48,172,173],{},"你看到的是 UTC 还是本地时间？",[16,175,176],{},"这三步能解决大多数排查问题。",[29,178,179],{"id":179},"常见开发场景",[16,181,182],{},"时间戳转换经常出现在这些任务里：",[45,184,185,188,191,194,197],{},[48,186,187],{},"检查 token 什么时候过期",[48,189,190],{},"阅读审计日志",[48,192,193],{},"排查定时任务执行时间",[48,195,196],{},"校验分析事件是否延迟",[48,198,199],{},"对照数据库记录与 API 输出",[16,201,202,203,207],{},"如果时间戳只是一个更大 JSON 对象中的字段，也可以先用 ",[23,204,206],{"href":205},"/dev/json-formatter","Anything Tools JSON Formatter"," 把结构整理清楚，再看日期字段会更省时间。",[29,209,210],{"id":210},"秒和毫秒的最快判断方法",[16,212,213],{},"如果你只记住一条经验规则，那就是先看位数：",[45,215,216,219],{},[48,217,218],{},"10 位数字通常是秒",[48,220,221],{},"13 位数字通常是毫秒",[16,223,224],{},"这不是数学定律，但在实际排查中非常有效，能快速挡掉大量低级错误。",[16,226,227],{},"另外也要警惕某些 API 文档写的是一种单位，实际通过中间层或 SDK 返回的却是另一种单位。",[29,229,230],{"id":230},"这些边界情况也别忽略",[16,232,233],{},"到了 2026 年，下面这些问题仍然值得留意：",[45,235,236,239,242,245],{},[48,237,238],{},"1970 年之前的负时间戳",[48,240,241],{},"老旧 32 位环境里的 2038 问题",[48,243,244],{},"夏令时切换导致的本地显示变化",[48,246,247],{},"JSON 中字符串和数字类型混用",[16,249,250],{},"现代浏览器和主流语言通常都能很好处理这些情况，但前提是你排查时足够明确。",[29,252,253],{"id":253},"一套可重复使用的排查流程",[16,255,256],{},"当某个时间值看起来可疑时，可以直接按这套流程走：",[163,258,259,262,265,268,271],{},[48,260,261],{},"复制原始时间戳。",[48,263,264],{},"先判断它是 10 位还是 13 位。",[48,266,267],{},"在浏览器里转换。",[48,269,270],{},"对比 UTC 和本地时间。",[48,272,273],{},"回溯这个字段来自哪个系统。",[16,275,276],{},"这样可以避免一种很常见的误区：表面上修的是展示 bug，实际上真正的问题是上游单位传错了。",[29,278,279],{"id":279},"结论",[16,281,282],{},"Unix 时间戳对机器很高效，但对人类并不友好。真正高效的做法，不是每次临时写脚本，而是手边一直有一套稳定的转换流程，并且先确认单位。",[16,284,285,286,288],{},"如果你需要一个轻量直接的方式来查看 epoch、互转日期，并快速区分秒和毫秒，可以从 ",[23,287,26],{"href":25}," 开始。",{"title":290,"searchDepth":291,"depth":291,"links":292},"",2,[293,294,295,296,297,298,299,300,301],{"id":31,"depth":291,"text":32},{"id":82,"depth":291,"text":82},{"id":105,"depth":291,"text":106},{"id":134,"depth":291,"text":135},{"id":179,"depth":291,"text":179},{"id":210,"depth":291,"text":210},{"id":230,"depth":291,"text":230},{"id":253,"depth":291,"text":253},{"id":279,"depth":291,"text":279},"开发者工具","2026-03-29T00:00:00.000Z","学习如何把 Unix 时间戳转换成人类可读日期，避开秒与毫秒混淆，并更高效地排查时间字段问题。","md",false,"/blog/how-to-convert-unix-timestamp-to-date.png",{},true,"/blog/zh-cn/how-to-convert-unix-timestamp-to-date",8,{"title":6,"description":304},"blog/zh-CN/how-to-convert-unix-timestamp-to-date",[315,316,317,318,302],"Unix 时间戳","Epoch 时间","日期转换","调试",[25],"KJJ5-xphStiQykU_6qywEmVTjmHtsRT4YgDv6UGWGEg",1781687068926]