Code
The YAML Editor shows your YAML code and the data as a tree side by side. Fold mappings and lists, see the type and the number of entries of every value, and change keys and values right in the tree - the change goes into the code at exactly that place, and your comments and formatting stay. Errors are listed with line and column, from a wrong indentation to a tab or an alias without its anchor, and the data can be checked against a JSON Schema and converted to JSON, CSV or XML.
Everything runs in your browser. Documents are not uploaded, there is no sign-up and no advertising.
Highlighted YAML 1.2 on the left, the foldable tree in the middle - one tree per document after ---. A click in the tree jumps to the code, the code cursor marks its value in the tree.
Change keys and values, add, duplicate, move and remove entries, change a type - each as a small edit of the code, so comments and blank lines stay where they are.
Wrong indentation, tabs, duplicate keys, aliases without their anchor and values that do not fit your JSON Schema, each with its line and column.
&anchor, *alias and merge keys (<<) are marked in the tree and resolved for conversions.
Format with consistent indentation, or convert to JSON, CSV (a list of mappings is a table) and XML. JSON, CSV and XML files open as YAML.
Keep any number of documents in your browser, with their own undo history, and download them all as a ZIP.
Any https page (and localhost) can embed the editor with an <iframe> and ?embed=1 - no sign-up, no key. Embedded, the editor hides this text and shows a Save button. There are two ways to get the document in and out.
src= opens a file (your server must allow CORS), webhook= makes "Save" (Ctrl+S) send the document to that address. Add &token=… for an Authorization: Bearer … header and &auto to save after every change.
<iframe src="https://yaml.giit.ch/?embed=1&src=https://your-site.com/config/app.yaml&webhook=https://your-site.com/save.php"
allow="clipboard-write" style="width:100%;height:800px;border:0"></iframe>The webhook gets a POST with JSON { editor: "yaml", event: "save", id, name, content, updated }; content is the document as a string. A small PHP script that stores it:
<?php
header('Access-Control-Allow-Origin: https://yaml.giit.ch');
header('Access-Control-Allow-Headers: Content-Type, Authorization');
header('Access-Control-Allow-Methods: POST, OPTIONS');
if ($_SERVER['REQUEST_METHOD'] === 'OPTIONS') exit;
if (($_SERVER['HTTP_AUTHORIZATION'] ?? '') !== 'Bearer SECRET') { http_response_code(403); exit; }
$d = json_decode(file_get_contents('php://input'), true);
$name = preg_replace('/[^\w\- ]/u', '_', $d['name']);
file_put_contents(__DIR__ . "/config/$name.yaml", $d['content']);
echo '{"ok":true}';The editor says yamleditor:ready, your page answers with yamleditor:load, the editor reports yamleditor:loaded, yamleditor:change on real edits and yamleditor:save when the user saves. Your page may send yamleditor:get (the current state) or yamleditor:save (press Save). Saving then goes through your own login and session.
<iframe id="ed" src="https://yaml.giit.ch/?embed=1" allow="clipboard-write" style="width:100%;height:800px;border:0"></iframe>
<script>
const ed = document.getElementById('ed');
const ORIGIN = 'https://yaml.giit.ch';
addEventListener('message', async e => {
if (e.source !== ed.contentWindow || e.origin !== ORIGIN) return;
const m = e.data;
if (m.type === 'yamleditor:ready') { // the editor is ready: hand it the document
ed.contentWindow.postMessage({
type: 'yamleditor:load',
name: 'Settings',
content: await (await fetch('/config/app.yaml')).text()
}, ORIGIN);
}
if (m.type === 'yamleditor:change') document.title = '● not saved'; // a real edit
if (m.type === 'yamleditor:save') { // the user clicked "Save"
await fetch('/api/save', { method: 'POST', headers: { 'Content-Type': 'application/json' },
body: JSON.stringify({ name: m.name, content: m.content }) });
document.title = 'Saved';
}
});
// A save button on your own page: the answer comes as yamleditor:save
function saveNow() { ed.contentWindow.postMessage({ type: 'yamleditor:get' }, ORIGIN); }
</script>AI Assistant inside your page: it works in the frame too. With allow="clipboard-write" on the iframe, "Copy prompt" uses the clipboard directly (otherwise the editor falls back to the old copy command, or shows the prompt to copy by hand). A link the AI sends cannot reach an editor inside another website, so the editor tells the AI and the user to paste the AI's whole answer into the editor instead - or open the editor in a window of its own.
window.open("https://yaml.giit.ch/?embed=window", "yamleditor-17") opens the full editor in its own window and speaks the same messages with window.opener. Links from an AI reach it there. yamleditor:load may also carry context: { host, title, rules } - the AI prompt then says where the document belongs and follows your rules - and hook: { url, token }, a webhook for this document only that is never stored. Closing the window with unsaved changes sends yamleditor:closing.
Hand the editor your own prompt, an address on your site and a key for this editor session. The AI dialog then shows "Connected to" your site, what you tell the AI, and the choice change the current document or make a new one; Copy prompt puts it all together. The AI posts its result with the key to your server, and your page opens it in the editor - a new document opens separately and stays in the user's browser. One key per editor session: it stays valid while the editor is open, and only while it has none the editor asks for it with yamleditor:key-request. The editor never sends the key itself and never stores it; the address must be https on your own host or a subdomain of it.
const key = async () => (await fetch('/api/ai-key.php?doc=17')).json(); // one key per editor session
const k = await key();
ed.contentWindow.postMessage({ type: 'yamleditor:load', name: 'Settings', content, ai: {
label: 'My Site', prompt: 'Keep every key and every comment.',
endpoint: 'https://your-site.com/api/ai-result.php', key: k.key } }, ORIGIN);
// remember the id from yamleditor:loaded and ignore change/save/closing with another id
// only while the editor has no key:
if (m.type === 'yamleditor:key-request') { const k = await key(); ed.contentWindow.postMessage({ type: 'yamleditor:ai', key: k.key }, ORIGIN); }
// while the editor is open, tell your server every minute; closing the editor or the page voids the key
setInterval(() => fetch('/api/ai-key.php?alive=' + k.key.slice(0, 8)), 60000);
// your server has a result (polling, SSE …): target is "current" or "new"
ed.contentWindow.postMessage({ type: 'yamleditor:load', name: 'Settings', content: draft, from: 'ai', target }, ORIGIN);Make keys with at least 128 random bits, store only their hash, bind each to the logged-in user, the document and this editor session, make one per session, keep it valid only while your page reports the session as open, and void it when the editor or the page closes.
The whole protocol is in llms.txt - give it to an AI and it builds the connection for your system. The JSON Editor works the same way with the prefix jsoneditor: - json.giit.ch.
No. The editor runs entirely in your browser. Your documents are never sent to a server, unless you set up a webhook to your own server yourself.
Yes. A change in the tree is written into the code at exactly that place; comments, blank lines and the rest of the formatting stay as they are. Undo takes every change back.
YAML does not allow tabs for indentation. The editor marks every place, and the Tab key in the code inserts spaces.
Yes. Anchors (&name) and aliases (*name) are marked in the tree, merge keys (<<) are resolved for conversions, an alias without its anchor is reported, and every document after --- gets its own tree.
Yes, in the Convert tab or under Export. A list of mappings becomes a CSV table. JSON, CSV and XML files you open are converted to YAML.
Only in your browser. Click the folder button at the top left (My documents) to open, rename, duplicate, download or delete them. Clearing your browser's site data removes them, so download the ones you want to keep - or let the editor send them to your own server ("Save to server").
Yes, any AI - ChatGPT, Claude, Gemini, Copilot or the AI in your coding tool. Click "AI Assistant", then "Copy prompt", paste it into your AI and say what it should change. The AI answers with a link; click it and the data appears in your editor. "Undo" takes every change back.
No. The editor is free, without ads and without sign-up.