Split a multi-document Kubernetes manifest into one file per resource, or join files into one. Comments, quoting and key order survive unchanged.
Waiting for a multi-document manifest
Each document comes back as its own file, sliced from your text unchanged.
The separate files appear here
Named kind-name.yaml, lowercased, which is the convention Kustomize and most repository layouts expect.
Each piece is sliced out of your text rather than rebuilt from a parse tree, so comments, quoting and key order survive exactly as written. That is deliberate: re-emitting YAML is easier and quietly destroys every comment in the file. Joining does not deduplicate or reorder anything, because deciding which of two resources with the same kind and name should win is not a decision this tool can make for you.
Kubernetes Manifest Splitter runs entirely on your device — nothing is applied, no cluster is contacted, and your manifests are never uploaded.
You’re on the Free plan. Compare plans
The design decision that matters is that nothing is re-emitted. Each document is sliced out of your source text rather than rebuilt from a parse tree. Re-emitting is easier and quietly destroys everything people actually care about: every comment, every deliberate quoting choice, every block scalar written `|-` rather than `|`, and the key order the author chose.
A tool whose job is "give me these as separate files" has no business reformatting them on the way through, so it does not. Paste a file with comments explaining why a toleration is there, and those comments come out the other side.
Filenames follow the `kind-name.yaml` convention, lowercased, which is what Kustomize and most repository layouts expect. A document with no name falls back to its position, because a collision between two files called `service-.yaml` is worse than an ugly filename.
Joining puts a three-dash separator between documents and does nothing else. It does not deduplicate, reorder, or resolve a conflict between two resources sharing a kind and a name — that would mean deciding which wins, and there is no basis for that decision here. Two identical resources in one file is a real thing to fix, and the inspector will tell you about it.
Nothing is applied and no cluster is contacted.
No. Each document is cut out of your text rather than regenerated, so comments, quoting style, indentation and key order all survive. That is the whole point — a splitter that reformats is a formatter you did not ask for.
`kind-name.yaml`, lowercased — `deployment-api.yaml`, `service-api.yaml`. That matches the Kustomize convention and most repository layouts. A document with no name is named by its position instead.
No, deliberately. If two documents declare the same kind and name, deciding which one wins is a judgement this tool cannot make for you, and silently dropping one would be worse than leaving both. The inspector reports the duplicate so you can choose.