Edit YAML files in your browser

In Easy editor, open Advanced YAML settings and Project schema rules. Import or write a version 1 project manifest, explicitly enter this file’s logical project name, review its attached-schema matches, then adopt it. Export shares your supplied logical names and schema identifiers; schema contents and attachment IDs stay local. Reattach schemas and review the manifest in a new session. Matching is exact and case-sensitive, with no inferred directories or URL fetching. Document overrides and manual filename choices, including No schema, take precedence over project rules and the editor default. Missing, replaced or conflicting attachments withhold project checks until another review. Check mapped project files separately reviews explicit labels for up to eight selected files and 25 MiB combined, then runs cancellable local workers. Results disclose each document’s schema coverage and incomplete checks. Project settings never edit YAML or add Undo entries.

Open Follow schema references from Advanced YAML settings. In Inspector, choose Original YAML or JSON documents, then Attach reference documents and select draft 7 or 2020-12 document references. In Source, place the cursor inside a static $ref value and use F12 or Follow reference, or Cmd/Ctrl-click the value. Following a reference selects the original target, including component paths; a target in the open document and Back select the actual Source editor without editing it. Relative links use each displayed resource URI, which you can explicitly review and change. The virtual URI is not a filesystem grant. Nothing is fetched and navigation does not change YAML or schema assignments. Original text stays in this session only: up to nine attachments, 1 MiB each. YAML requires one safe JSON projection and exact original positions; aliases, unsupported tags, unsafe values, ambiguous identifiers and missing resources remain unavailable. This is static navigation, not OpenAPI validation or dynamic-reference evaluation. The separate attached JSON Schema mode retains its 2020-12 active-schema behavior.

Yes. Leading file-header comments using yaml-language-server $schema or the $schema comment form appear as suggestions in Inspector and Advanced YAML settings. Nothing is fetched or applied automatically. Explicitly attach the schema first; only an unambiguous absolute identifier matches attached resources. Relative paths, URI fragments and conflicting declarations remain manual choices. Use attached modeline schema for Document N creates only that document override, preserving existing overrides and No schema. Source and other document assignments stay unchanged. Reattaching allocates a new identity: a reviewed assignment becomes unavailable instead of silently following a replacement or default. Select a schema manually or remove the override and review again. Manual document selection clears reviewed-modeline provenance. Header inspection and catalog matching have explicit work limits; legacy ambiguous aliases may need reattachment.

Open Query document, explicitly choose one document and enter a JSONata expression. Run YAML query evaluates locally in a cancellable worker; download a separate JSON result copy. The original YAML, comments, anchors and other documents stay unchanged. This is JSONata, not yq. Only safely JSON-representable data is accepted. Query limits are 2,000,000 source and result characters, 10,000 expression characters and 5 seconds; JSON conversion limits syntax work to 100,000 nodes; arithmetic proof separately limits input work to 100,000 values and containers. The owning alias-expansion limit also applies; intermediate worker memory can be larger. JSONata uses JavaScript numbers. Only provably safe integer arithmetic is admitted. Decimal arithmetic, unknown ranges and unbounded function inputs are refused. Precision-sensitive input, literals and text conversions are refused, and dynamic $eval is unavailable. This is not an exact decimal arithmetic engine. Pending field drafts must be applied or discarded. Source, document choice, expression, schema/settings or draft changes invalidate the result before download.

Easy editor shows 100 direct fields at a time within the 10,000-node outline limit. Use Previous fields and Next fields to navigate. Apply or discard pending field edits before changing pages. Closing and reopening Tools retains the draft and current page; Source search remains available for additional values.

Load local JSON Schema files in Advanced YAML settings. Inspector and Advanced YAML settings show the effective schema and whether it comes from a document override, filename assignment, reviewed project rule or editor default. Document overrides take precedence over filename assignments, then reviewed project rules, then the editor default. Choose Use editor default to remove a filename override, or No schema to keep syntax checks without schema validation. A missing assigned schema is shown as unavailable until imported again. Local references stay local. Unsupported precision or dialect cases are shown as warnings. Schema completion and hover are withheld for a document whose JSON projection has unsupported numbers, keys or alias expansion; a safe sibling document keeps hints. For numeric projection limits, continuous diagnostics omit conditional, reference and numeric checks while retaining independent unconditional checks. Unsupported keys or alias expansion retain syntax checks only. Full schema validation remains unavailable for these cases, and schema-reviewed assistance cannot apply on an incomplete result. Source values and syntax checks remain available.

Yes. Open Compare and merge, then choose Other version to compare it with the current document. The common Original version is optional and only needed for three-way merging. Review conflicts before applying a merge; Undo restores the prior source.

Filter keys and use Previous outline page or Next outline page to inspect up to 1,000 nodes at a time. The outline has a 10,000-node safety limit; Source search remains available beyond the displayed outline.

Open a .yaml or .yml file or paste your YAML. Edit the text in Source or use the Easy editor for supported values. Check syntax, review differences and download your edited YAML.

Yes. The editor supports undo and a differences view so you can review changes before downloading. Keep the original file when checking configuration changes.

Local editing parses YAML in your browser. Optional Assistance sends only your goal and source text you explicitly select and include to the displayed processing destination. The browser uses OpenRouter and its configured model provider; installed desktop versions offering a local option can use your configured Ollama service instead. Ordinary page and asset requests also reach the hosting provider.

No. Whole-file JSON export is unavailable for multiple documents. Explicit tags, non-string or complex keys, exact numbers and excessive alias expansion can also require YAML source. Read-only Query document selects one document explicitly and only accepts its safe JSON representation.

Back to website and Resume retain edits in this tab. Refresh first opens the original input; matching local source snapshots can then be previewed and explicitly restored as one undoable edit. Recovery offers expire after 24 hours, storage can fail, and unapplied form drafts are not included. Download important YAML separately.