[{"data":1,"prerenderedAt":229},["ShallowReactive",2],{"page:/zh/guides/seconds-vs-milliseconds/":3},{"id":4,"title":5,"body":6,"description":215,"extension":216,"eyebrow":217,"faq":218,"locale":219,"meta":220,"navigation":221,"pageType":222,"path":223,"related":218,"seo":224,"stem":227,"__hash__":228},"pages/zh/guides/seconds-vs-milliseconds.md","Unix 秒与毫秒的区别",{"type":7,"value":8,"toc":203},"minimark",[9,13,30,34,37,40,51,54,57,60,135,147,151,154,169,172,185,188,191],[10,11,12],"h2",{"id":12},"相差一千倍",[14,15,16,17,21,22,25,26,29],"p",{},"秒统计纪元后经过的整秒，毫秒统计千分之一秒，所以同一时刻的毫秒值是秒值的 1,000 倍。例如，",[18,19,20],"code",{},"1700000000 s"," 和 ",[18,23,24],{},"1700000000000 ms"," 都对应 ",[18,27,28],{},"2023-11-14T22:13:20Z","。",[10,31,33],{"id":32},"为什么位数只是提示","为什么位数只是提示？",[14,35,36],{},"当代正数通常是 10 位秒或 13 位毫秒，但靠近纪元的值更短，负数带符号，未来值会增长。可靠程序应接受明确单位，或至少向用户显示自动识别结果。",[10,38,39],{"id":39},"精度与安全整数",[14,41,42,43,46,47,50],{},"JavaScript Number 只能在 ",[18,44,45],{},"Number.MAX_SAFE_INTEGER"," 以内精确表示整数。本站换算 epoch 单位时使用 ",[18,48,49],{},"BigInt","，避免 16 位或 19 位输入在计算毫秒日期之前就被舍入。最终日期显示仍受浏览器毫秒精度和日期范围限制。",[10,52,53],{"id":53},"排查一千倍错误",[14,55,56],{},"如果日期落在 1970 年附近，常见原因是把秒当成毫秒；如果结果遥远到超出范围，则可能把毫秒当成秒。先核对字段文档，再手动选择单位，比只看位数更可靠。",[10,58,59],{"id":59},"四种单位表示同一时刻",[61,62,63,79],"table",{},[64,65,66],"thead",{},[67,68,69,73,76],"tr",{},[70,71,72],"th",{},"单位",[70,74,75],{},"数值",[70,77,78],{},"相对于秒的倍数",[80,81,82,96,109,122],"tbody",{},[67,83,84,88,93],{},[85,86,87],"td",{},"秒",[85,89,90],{},[18,91,92],{},"1700000000",[85,94,95],{},"1",[67,97,98,101,106],{},[85,99,100],{},"毫秒",[85,102,103],{},[18,104,105],{},"1700000000000",[85,107,108],{},"1,000",[67,110,111,114,119],{},[85,112,113],{},"微秒",[85,115,116],{},[18,117,118],{},"1700000000000000",[85,120,121],{},"1,000,000",[67,123,124,127,132],{},[85,125,126],{},"纳秒",[85,128,129],{},[18,130,131],{},"1700000000000000000",[85,133,134],{},"1,000,000,000",[14,136,137,138,140,141,146],{},"这四个数值都对应 ",[18,139,28],{},"。乘以 1,000 是更换单位，不是改变时刻，也不会增加真实测量精度。可在",[142,143,145],"a",{"href":144},"/zh/timestamp-to-date/","转换工具","中逐一输入并手动选择对应单位。",[10,148,150],{"id":149},"为什么结果跑到-1970-年或很远的未来","为什么结果跑到 1970 年或很远的未来？",[14,152,153],{},"现代事件被显示成 1970 年 1 月，常见原因是把秒按毫秒解释；出现几万年后的日期，则可能把毫秒当成秒。应先核对源系统字段文档，而不是先修改数值。10 位、13 位只适合辅助识别当代常见数据，不能作为所有日期的通用规则。",[14,155,156,157,160,161,163,164,168],{},"例如 ",[18,158,159],{},"1000"," 秒是 1970-01-01 00:16:40 UTC，",[18,162,159],{}," 毫秒却是当天 00:00:01，两者都合法。处理来源单位统一的文件时，可以在",[142,165,167],{"href":166},"/zh/batch-converter/","批量转换器","中固定单位，避免历史数值被误判。",[10,170,171],{"id":171},"精度损失与负数取整",[14,173,174,177,178,181,182,184],{},[18,175,176],{},"1700000000123"," 毫秒比对应的整秒多出 123 毫秒，转为整数秒后这部分会丢失。本工具按所处单位区间的起点向下取整，因此 ",[18,179,180],{},"-1"," 纳秒属于毫秒 ",[18,183,180],{},"，而不是毫秒零。",[14,186,187],{},"微秒、纳秒输出保留原始整数精度；ISO 日历日期显示到毫秒，有更细的余数时会提示。数据库审计或精确往返转换时，应保留原始整数，仅保存可读日期无法还原毫秒以下的细节。",[10,189,190],{"id":190},"标准与运行时参考",[192,193,194],"ul",{},[195,196,197],"li",{},[142,198,202],{"href":199,"rel":200},"https://tc39.es/ecma262/multipage/numbers-and-dates.html#sec-time-values-and-time-range",[201],"nofollow","ECMAScript Date time values",{"title":204,"searchDepth":205,"depth":205,"links":206},"",2,[207,208,209,210,211,212,213,214],{"id":12,"depth":205,"text":12},{"id":32,"depth":205,"text":33},{"id":39,"depth":205,"text":39},{"id":53,"depth":205,"text":53},{"id":59,"depth":205,"text":59},{"id":149,"depth":205,"text":150},{"id":171,"depth":205,"text":171},{"id":190,"depth":205,"text":190},"比较 10 位和 13 位时间戳，理解单位识别、精度、存储范围和常见转换错误。","md","指南 / 精度",null,"zh",{},true,"guide","/zh/guides/seconds-vs-milliseconds",{"title":225,"description":226},"Unix 时间戳秒与毫秒 — 10 位还是 13 位？","理解 Unix 秒和毫秒的区别，识别常见 10 位与 13 位数值并安全转换。","zh/guides/seconds-vs-milliseconds","-5L5ZJ-LKnF1B1-TAsljnwWCiWUF2FGwwRCESk7RYdY",1792032487956]