CSV to Markdown Frontmatter

A header row of field names followed by one row per document. Each data row becomes its own --- frontmatter block, with the column headers as the YAML keys, in the order your columns appear.

A cell containing a comma-separated list (like tags) is converted into a real YAML array, so "astro,blog" becomes ["astro", "blog"] rather than a single string. A value with a single trailing comma, like "astro,", is left as the plain string it looks like rather than guessed at.

A cell that is exactly "true" or "false" becomes a real YAML boolean, and a plain integer or decimal becomes a real number - both unquoted, so downstream tools read them as their actual type rather than text. Dates are quoted like any other string: whether a bare date becomes a native timestamp is parser-specific (Jekyll's Ruby parser does that; many JavaScript YAML libraries do not), so quoting keeps the value predictable everywhere instead of shipping a guess. A number with a leading zero, like a "0755" zip code, is also kept quoted, because some YAML parsers read a leading zero as octal notation and would silently change its value.

Pick the matching delimiter from the dropdown. Everything else - quoted fields, embedded commas inside quotes, list-splitting - works the same regardless of which delimiter separates your columns.

Switch the Quote character dropdown to single quote (') before generating. The parser then treats ' the way it normally treats " - for quoting a field, escaping an embedded quote by doubling it, and allowing commas or line breaks inside a quoted value.

Yes - set Array style to "Block: indented list" and comma-separated cells render as an indented "- item" list under their key instead of one inline [a, b, c] line, with a choice of 2- or 4-space indent. Both styles parse to the identical array value; it's a formatting preference, not a behavior change.

The tool still generates a block for it: extra values past the last column are dropped, and missing values are treated as empty, with a note above the results telling you which row numbers were affected so you can go back and fix the source CSV if that was a mistake.

No - it only generates the --- frontmatter block from your CSV columns. The body content still needs to be written or pasted in separately.

One combined frontmatter.md file containing every row's block in order, separated by their own --- delimiters. If you need each row as its own file, copy blocks individually and save them under separate filenames.

Yes - the output is standard YAML between --- delimiters, the same format all three (and most other static site generators) expect at the top of a content file. Nothing here is framework-specific. The "Load sample" dropdown includes a ready-made CSV for each of Astro, Jekyll, Hugo, and Obsidian, using that platform's own documented frontmatter field names, so you can see real column names before wiring up your own CSV.

No - parsing and conversion happen entirely in your browser. Your CSV rows are never sent to a server, which also means there is no file-size or row-count limit beyond what your browser can handle.