Loading page
About this tool
Split multi-document YAML on --- markers into separate validated files, suggest filenames, and recombine them cleanly.
A YAML multi document splitter breaks a single YAML stream into its individual documents at the `---` markers defined by the YAML 1.2 specification, then validates and names each one. It is built for anyone holding a bundled Kubernetes manifest, a Docker Compose override set or a CI pipeline file that has grown into one long stream. Separators that appear inside a block scalar (`|` or `>`) are treated as literal text, so a document is never cut in the wrong place.
Open YAML Multi Document Splitter on AltFTool — it loads instantly in your browser.
Paste or upload your source content.
Choose the target format or conversion mode.
Copy or download the converted result.
A `---` inside a `|` or `>` literal block stays part of the text instead of splitting the file.
Each document is parsed on its own so one bad document does not hide the others.
Kubernetes documents are named `<kind>-<metadata.name>`, so files land with meaningful names.
Cut the file at every line that is exactly `---` at column 0, and close a document at any line that is exactly `...`. Those two markers are the document start and end indicators in the YAML 1.2 specification; every other `---` — including one inside a quoted string or a block scalar — is ordinary content.
It marks the start of a new document, letting one file hold several independent objects such as a Deployment, a Service and a ConfigMap. `kubectl apply -f file.yaml` reads the whole stream and creates each document as a separate resource.
No. An anchor such as `&defaults` and its alias `*defaults` are only valid inside the document that defines them, so a stream that relies on an anchor from an earlier document will fail once the documents are split. Repeat the anchored block in each file, or keep those documents together.
`---` starts a document, while `...` ends the current document without starting another. `...` is optional and mainly useful in streams sent over a socket or appended to over time, where a reader needs to know the document is complete before more bytes arrive.