[{"data":1,"prerenderedAt":190},["ShallowReactive",2],{"page-zh-TW":3,"article-list-zh-TW":127,"article-zh-TW-terms":153},{"id":4,"title":5,"body":6,"description":17,"extension":18,"eyebrow":19,"faqIntro":20,"faqLabel":21,"faqTitle":22,"faqs":23,"footerRule":42,"footerRuleLabel":43,"footerTagline":44,"guideIntro":45,"guideLabel":46,"guideTitle":47,"intro":48,"meta":49,"navigation":50,"openTool":51,"path":52,"pitfalls":53,"pitfallsIntro":66,"pitfallsLabel":67,"pitfallsTitle":68,"reasons":69,"referenceIntro":82,"referenceLabel":83,"referenceNoteLabel":84,"referenceRows":85,"referenceTitle":110,"seo":111,"seoTitle":112,"stem":113,"steps":114,"workflowLabel":124,"workflowTitle":125,"__hash__":126},"pages\u002Fzh-tw\u002Findex.md","YAML 轉 JSON 轉換器",{"type":7,"value":8,"toc":13},"minimark",[9],[10,11,12],"p",{},"不必將來源傳送到轉換伺服器，即可把 YAML 設定與資料轉成標準 JSON。",{"title":14,"searchDepth":15,"depth":15,"links":16},"",2,[],"在瀏覽器中將 YAML 轉換為有效 JSON。支援多文件、縮排、複製與下載，不需上傳檔案。","md","專注的 YAML 工作區","解答 YAML 中無法完整對應到 JSON 的部分。","05 \u002F 參考問答","YAML 轉換常見問題",[24,27,30,33,36,39],{"question":25,"answer":26},"我的 YAML 會被上傳嗎？","不會。解析、JSON 產生、複製與下載準備都在瀏覽器中完成。",{"question":28,"answer":29},"是否支援多個 YAML 文件？","支援。以 --- 分隔的文件會作為一個 JSON 陣列回傳。",{"question":31,"answer":32},"支援哪個 YAML 版本？","解析器採用 YAML 1.2 行為，可避免 YAML 1.1 中部分意外的布林值轉換。",{"question":34,"answer":35},"所有 YAML 功能都能轉成 JSON 嗎？","不能。JSON 的資料模型較小，註解、錨點、標籤與原始格式不會保留。",{"question":37,"answer":38},"YAML 錨點與別名會如何處理？","解析器會展開別名，JSON 接收解析後的實際值；錨點名稱、別名與合併語法不會保留。",{"question":40,"answer":41},"為什麼某個 YAML 值的類型改變了？","未加引號的 YAML 純量可能是字串、數字、布林值或 null。帶前導零的識別碼與類似日期的文字應加上引號。","瀏覽器本機處理、不需帳戶、輸出標準 JSON。","處理原則","將人類可讀設定轉換為嚴格資料的專用工具。","掌握彈性 YAML 文件轉換為嚴格 JSON 時最重要的細節。","02 \u002F YAML 筆記","謹慎處理 YAML，穩定產生 JSON。","將易讀的 YAML 轉成嚴格 JSON，提供清楚的語法回饋，且不需上傳內容。",{},true,"開啟轉換器","\u002Fzh-tw",[54,57,60,63],{"title":55,"body":56},"註解不是資料","YAML 註解有助閱讀，但不屬於解析後的值。JSON 無法保留註解內容及原本位置。",{"title":58,"body":59},"錨點會被展開","別名與合併鍵可減少 YAML 重複內容；JSON 結果只保留展開後的值，不保留錨點名稱與語法。",{"title":61,"body":62},"對應鍵必須成為字串","JSON 物件的鍵只能是字串。使用複雜鍵或非字串鍵的 YAML 對應需要額外檢查。",{"title":64,"body":65},"日期形式的文字建議加引號","不同 YAML 工具可能用不同方式解析類似日期的純量。若必須保留文字，請明確加上引號。","轉換會保留 JSON 能表示的資料。註解、排版及 YAML 特有功能沒有標準 JSON 對應語法，因此只能被解析或捨棄。","04 \u002F 轉換限制","JSON 無法繼續承載的資訊",[70,74,78],{"title":71,"body":72,"icon":73},"理解 YAML 的錯誤提示","解析失敗時保留行號與來源內容，不會只回傳空白結果。","lucide:scan-line",{"title":75,"body":76,"icon":77},"支援多文件","以 --- 分隔的 YAML 串流會轉成 JSON 陣列，不會靜默遺失文件。","lucide:layers-3",{"title":79,"body":80,"icon":81},"預設在瀏覽器本機執行","文字與本機檔案只在目前分頁處理，不需要帳戶或伺服器佇列。","lucide:shield-check","常見結構通常可以直接對應，但 YAML 的資料模型比 JSON 更豐富。將設定交給 API 或應用程式前，可先利用此表確認轉換結果。","03 \u002F 類型對應","轉換說明",[86,90,94,98,102,106],{"yaml":87,"json":88,"note":89},"name: Ada","\"name\": \"Ada\"","YAML 的純量字串和帶引號字串都會成為使用雙引號的 JSON 字串。",{"yaml":91,"json":92,"note":93},"enabled: true","\"enabled\": true","YAML 1.2 布林值會保留為布林值；yes 和 no 會視為字串。",{"yaml":95,"json":96,"note":97},"count: 42","\"count\": 42","一般整數和小數會成為 JSON 數字，並受 JavaScript 數字精度限制。",{"yaml":99,"json":100,"note":101},"items: [a, b]","\"items\": [\"a\", \"b\"]","區塊與流式序列都會成為 JSON 陣列，項目順序維持不變。",{"yaml":103,"json":104,"note":105},"value: null","\"value\": null","YAML 的 null 和空值通常都會轉換為 JSON null。",{"yaml":107,"json":108,"note":109},"--- \u002F ---","[{…}, {…}]","多份 YAML 文件會放入同一個 JSON 陣列，避免遺漏任何文件。","YAML 值轉成 JSON 後的樣貌",{"title":5,"description":17},"YAML 轉 JSON 線上轉換器 - 瀏覽器本機處理","zh-tw\u002Findex",[115,118,121],{"title":116,"body":117},"加入 YAML","貼上 YAML、載入內建範例，或選擇本機 .yaml、.yml 檔案。",{"title":119,"body":120},"本機轉換","瀏覽器依 YAML 1.2 解析資料，並序列化為標準 JSON。",{"title":122,"body":123},"使用結果","複製格式化 JSON，或下載 UTF-8 檔案供 API、應用程式、測試與遷移使用。","01 \u002F 轉換流程","從易讀設定到嚴格資料","onPCTeF2ri8p0GYYGMY1-2jaQaD8ramd5BACbdP0288",[128,133,138,143,148],{"slug":129,"title":130,"description":131,"eyebrow":132},"fix-invalid-yaml","如何修復無效 YAML","在轉換為 JSON 前，排查 YAML 的縮排、定位字元、冒號、引號與清單錯誤。","錯誤排查",{"slug":134,"title":135,"description":136,"eyebrow":137},"multiple-yaml-documents-to-json","將多個 YAML 文件轉換為 JSON","了解由 --- 分隔的 YAML 文件流如何轉換成清楚、可攜的 JSON。","YAML 文件流",{"slug":139,"title":140,"description":141,"eyebrow":142},"yaml-anchors-aliases-json","YAML 錨點和別名轉換為 JSON","了解 YAML 錨點、別名和合併鍵在轉換為 JSON 時如何展開。","錨點與別名",{"slug":144,"title":145,"description":146,"eyebrow":147},"yaml-data-types-to-json","YAML 資料類型如何轉換為 JSON","了解 YAML 字串、數字、布林值、null、日期和標籤值如何映射到 JSON。","資料類型",{"slug":149,"title":150,"description":151,"eyebrow":152},"yaml-vs-json","YAML 與 JSON：語法、優勢和轉換限制","比較 YAML 和 JSON 的語法、類型、註解、錨點，以及轉換過程中可能發生的資訊變化。","格式比較",{"id":154,"title":155,"body":156,"description":160,"extension":18,"eyebrow":161,"faqs":162,"intro":163,"meta":164,"navigation":50,"path":165,"relatedGuides":162,"sections":166,"seo":183,"seoTitle":184,"slug":185,"stem":186,"type":187,"updated":188,"__hash__":189},"articles\u002Fzh-tw\u002Farticles\u002Fterms.md","使用條款",{"type":7,"value":157,"toc":158},[],{"title":14,"searchDepth":15,"depth":15,"links":159},[],"瀏覽器本機 YAML 轉 JSON 工具的使用條款。","法律資訊",null,"本條款說明 yamltojson.org 的允許用途與實際限制。",{},"\u002Fzh-tw\u002Farticles\u002Fterms",[167,171,175,179],{"title":168,"paragraphs":169},"服務範圍",[170],"網站提供免帳戶的瀏覽器轉換工具，不承諾固定服務等級。解析器、瀏覽器與網站更新都可能改變功能。",{"title":172,"paragraphs":173},"使用者責任",[174],"在生產環境、敏感設定或自動化部署中使用前，請檢查轉換後的 JSON 並確認符合目標結構。",{"title":176,"paragraphs":177},"合理使用",[178],"不得干擾網站運作、散播惡意程式碼、未經授權測試系統或違反適用法律。",{"title":180,"paragraphs":181},"可用性與責任",[182],"工具依現況提供，不保證持續可用。請勿依賴未經檢查的轉換結果。",{"title":155,"description":160},"使用條款 — yamltojson.org","terms","zh-tw\u002Farticles\u002Fterms","legal","2026 年 10 月 9 日","f8qOvo6UCV4cBYBKYcmTJOoxlro6a78ss4KUW01MQCI",1791972537059]