This generator vs. a hosted docs platform's built-in llms.txt feature
Several documentation hosting platforms now generate an llms.txt automatically, as one feature of moving your whole docs site onto their platform. This free tool builds and validates the same spec-compliant file from docs you already have — hosted anywhere — with no migration and no recurring cost.
What each one is for
A hosted documentation platform that auto-generates llms.txt does so as one bundled feature of its whole pipeline: your content lives on that platform, and because it controls every step from authoring to publishing, it can regenerate the file automatically the moment a page changes. That convenience comes with the platform's own pricing, its own authoring format, and a migration of docs that may already live somewhere else.
This generator does not need your docs to live
anywhere in particular. Paste a short page list, paste a
sitemap.xml you already publish, or point the CLI at a
local Markdown tree, and it produces a correctly structured llms.txt
— plus a validator, in the same tool, for one you already have.
Nothing is uploaded, there is no account, and nothing about your
documentation has to move.
It exists because the two are answering different questions. "Where should our documentation be hosted" is a real decision with real tradeoffs that has nothing to do with one file. "Do we have a spec-correct llms.txt today" is a much narrower question, and this tool answers it for free without requiring the first decision at all. See what llms.txt is, and whether you need one for the background.
| Question | Where to answer it |
|---|---|
| Do we need a correctly structured llms.txt today? | This generator — free, in your browser, no account, no migration. |
| Is our existing llms.txt actually valid? | This generator's validate tab. |
| Should we move our whole docs site to a new host? | A separate, larger decision this tool does not evaluate. |
| Do we want the file regenerated automatically on every deploy? | Wire cli.mjs's --dir or --sitemap mode into your own build script — no migration needed for that either. |
| Is anything we paste in uploaded anywhere? | No. Everything runs in this browser tab; the CLI reads local files or a sitemap URL you name. |
This generator is a formatting and validation tool, not a documentation host. It does not publish, store, or serve your documentation, and it does not evaluate which hosting platform is the right choice for your team.
This tool needs no account and no sign-in: it is a static page, building and validating run in your browser, and nothing you paste is uploaded anywhere.
Common questions
Should I use this generator or switch to a hosted docs platform that builds llms.txt automatically?
Depends why you would be switching. Moving your whole documentation site to a new host is a large decision — pricing, migration effort, and lock-in to that platform's authoring format — that should be justified by more than one file. If you already publish docs, on any host or none at all, and just need a correctly structured llms.txt today, paste your existing sitemap.xml or a short page list into this generator for free — no migration required.
Does this tool keep my llms.txt updated automatically the way a hosted platform would?
Not on its own — the browser tool is a point-in-time build. A hosted docs platform that owns your whole publishing pipeline can regenerate the file the moment a page is added or removed, because it controls every step. This tool gets you the same automatic-on-deploy behavior a different way: wire the CLI's --dir or --sitemap mode into your own build or deploy script, and it regenerates on every push without migrating anything.
What does this generator's validator check that a hosted platform's built-in generator gets right automatically?
The structural shape the llmstxt.org convention actually requires: an H1 title, an optional blockquote summary, and Markdown link bullets grouped under "## Section" headings. A hosted platform's own generator gets this right by construction, since it controls the whole pipeline end to end. This tool checks the same shape explicitly instead, because it doesn't control your pipeline — you can paste any llms.txt, from any source, into the validator tab and get the identical structural check.
Why not just migrate to a docs platform that includes this feature?
Proportionality. Moving your documentation hosting to gain one auto-generated file is a large move if that file is the only feature you actually want, and it ties the file's freshness to staying on that vendor's platform going forward. This generator produces the identical structural file today, from documentation hosted wherever it already lives, at no cost and with nothing to migrate.
Open the llms.txt Generator, or read what llms.txt is, and whether you need one.