[{"data":1,"prerenderedAt":321},["ShallowReactive",2],{"tool-related-posts-/zh-TW/dev/timestamp-zh-tw":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-TW/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],{},"大多數時間戳 bug 不是算式錯了，而是脈絡不夠清楚：",[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 payload 或複製出來的 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-tw/how-to-convert-unix-timestamp-to-date",8,{"title":6,"description":304},"blog/zh-TW/how-to-convert-unix-timestamp-to-date",[315,316,317,318,302],"Unix 時間戳","Epoch 時間","日期轉換","除錯",[25],"1bY36oj0cdK8axFhSmqemkVas_TgQGHa6x9lwJgmvl4",1781687123731]