Read the metadata block at the top of a Markdown file — YAML, TOML or JSON — as text, with no parser evaluating it, and see the body it sits above.
Waiting for Markdown
YAML between ---, TOML between +++, or a JSON object. Read as text, never evaluated.
Front matter appears here
Every top-level key with its line and its value, plus the body it sits above.
Front Matter Inspector runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Static site generators put a metadata block at the top of each Markdown file: YAML between ---, TOML between +++, or a JSON object. This reads it and shows you what is in it, alongside the body it belongs to.
Nothing is evaluated, and that is a deliberate design decision rather than a limitation that happened. YAML is not a simple format — it has tags that instruct a parser to construct arbitrary objects, and a string of real vulnerabilities over the years has come from tools loading untrusted YAML with a permissive loader. Reading the block as lines of text cannot do that, no matter what is in the file.
The practical consequence is that this is an inspector rather than a parser. tags: [cron, scheduling] comes back as the string [cron, scheduling], not as an array. For reading what a file declares, spotting the key you misspelled, and checking that a block is shaped the way the generator expects, that is exactly enough.
The most common real failure it catches is a block that opens and never closes. A missing second --- means everything below it is read as metadata, and most generators fail the build with a message that points at the wrong line. Here it is stated plainly, with the line the block started on.
A --- further down a document is a horizontal rule, not a metadata block, and is treated as one. Front matter only counts when it is the very first thing in the file.
No, deliberately. It reads the block as text and reports the top-level keys. YAML has tags that can instruct a parser to construct arbitrary objects, and loading untrusted YAML has produced real vulnerabilities, so nothing here evaluates anything.
Because an indented line belongs to the key above it, and presenting nested structure accurately would mean actually parsing the format. The top-level keys are what you usually need to check.
YAML between --- markers, TOML between +++ markers, and a JSON object at the very start of the file. All three are common across static site generators.
Because front matter has to be the first thing in the file. A --- further down is a horizontal rule, and treating it as a metadata block would break every document that uses one.
It is flagged clearly, with the line the block opened on. That is the most common front matter failure and most generators report it with a message pointing somewhere unhelpful.
No, it only reads. Writing front matter means serialising values back into YAML or TOML correctly, which needs the parsing this tool deliberately avoids.