Best llms.txt Generators in 2026
Short answer: Mintlify and GitBook already write llms.txt and llms-full.txt automatically, free, the moment you publish docs there. Firecrawl is the best pick for any other website: free up to 1,000 credits a month, then $16/mo for 5,000. Fern matches that free-forever deal and adds a dashboard on which AI bots actually read the file. Running Docusaurus or VitePress, add a free community plugin instead of switching platforms. Keploy's web tool needs no signup for a single one-off file.
Nine tools that build the file, picked for whether you already host docs somewhere or need one for any website.
Mintlify and GitBook are the easiest llms.txt generators in 2026, because both already build the file for you, free, the moment your docs are live there. Anthropic, Cursor, Pinecone and Windsurf all get their llms.txt this way, with no separate tool to buy. That head start does not help a marketing site, a blog, or an app that never touches a docs platform, which is where a crawler like Firecrawl or a sitemap tool like Keploy takes over instead.
Toolradar data: of the 170 documentation tools in the catalog, 76% ship a free or freemium plan and 41 (24%) are paid only, so a free llms.txt option is the norm in this category, not the exception. The harder question is not whether a free tier exists, but whether it covers your page count, your framework, or only the pages you host on that one platform.
This guide covers the tools that build the llms.txt file itself, not the broader practice of getting an AI model to cite you. For that wider strategy, see GEO tools and AEO and GEO tools. A crawler that also audits a whole site for AI readiness belongs in web scraping tools, and a platform built for classic search rankings sits in AI SEO tools. Teams weighing a full documentation platform switch, not just the one file, should also read documentation tools.
How we ranked: these 9 were picked from the 170 tools in documentation for how directly each one produces a working llms.txt, not for general documentation features. Every price below was verified on the vendor's own pricing page in September 2026, and none of these placements is paid.
Top Picks
Picked by editorial review, informed by G2 and Capterra review volume and rating and by media mentions, the signals behind our category rankings. How we rate
| Tool | Starting price | Rating | Best for |
|---|---|---|---|
| Mintlify | Free (Starter), Pro $450/mo | 4.619 reviews | Teams already on Mintlify, or picking a docs platform and wanting the file free from day one |
| Firecrawl | Free, then Hobby $16/mo | 4.848 reviews | Any site that isn't on a docs platform: a blog, a marketing site or a full domain crawl |
| Fern | Free forever (1,000 pages) | n/a | API-first teams that want the file plus proof an AI model is actually requesting it |
| GitBook | Free, Premium $65/site/mo | 3.9251 reviews | Teams already writing docs or wikis in GitBook who want the file with no plan upgrade |
| ReadMe | Free (Starter), Pro $250/mo | 4.546 reviews | API-first teams that want an interactive reference and llms.txt on one free plan |
| Docusaurus | Free, open source (MIT) | n/a | Teams already running Docusaurus who are comfortable installing one npm package |
| VitePress | Free, open source (MIT) | n/a | Vite or Vue ecosystem projects on VitePress that want proven plugin adoption |
| Keploy | Free tool, no signup | 4.950 reviews | A quick, one-off llms.txt when you don't want to install anything or sign up |
| Apify | Free ($5/mo credits) | 4.71,201 reviews | Developers who want a repeatable, schedulable crawl across more than one site |
Teams already on Mintlify, or picking a docs platform and wanting the file free from day one
Mintlify's pricing is fair for individuals and small teams, with a generous Hobby tier offering full platform access for free.
Any site that isn't on a docs platform: a blog, a marketing site or a full domain crawl
Firecrawl's pricing is quite fair, especially for the lower tiers, offering good value for developers and small businesses.
Watch out
Overage fees for extra credits can add up.
API-first teams that want the file plus proof an AI model is actually requesting it
Fern Docs Hobby is $0 forever: 2 members, 250 AI credits, custom domain, password-protected docs.
Watch out
Team yearly is 25% off. They do not print the yearly dollar total. Do the math at checkout.
Teams already writing docs or wikis in GitBook who want the file with no plan upgrade
GitBook's pricing is fair, especially with a robust free tier for personal use.
API-first teams that want an interactive reference and llms.txt on one free plan
ReadMe's pricing is generally fair, offering a generous Free tier and a well-structured progression.
Teams already running Docusaurus who are comfortable installing one npm package
Docusaurus offers an incredibly generous pricing model, as it is entirely free and open-source.
Vite or Vue ecosystem projects on VitePress that want proven plugin adoption
A quick, one-off llms.txt when you don't want to install anything or sign up
Keploy's Playground tier is incredibly generous, offering significant testing capabilities for free, making it highly accessible for individual developers and small teams.
Watch out
Overage charges for usage beyond Pro credit
Developers who want a repeatable, schedulable crawl across more than one site
The credit-based model means you pay for what you use (compute, storage, proxy bandwidth), but costs can be unpredictable, a single misconfigured Actor can burn through credits in hours.
Watch out
Platform credits are consumed by compute (Actor runs), storage (datasets, key-value stores), and proxy bandwidth, all three meters run simultaneously
What an llms.txt generator actually is
An llms.txt generator produces the Markdown file that lives at yourdomain.com/llms.txt, a short index of your most important pages that an AI model can read without crawling or parsing HTML first. The llmstxt.org proposal defines the format: a title, a summary, and a linked list of pages, each with a one-line description.
Three real approaches exist. A hosted docs platform like Mintlify, Fern, GitBook or ReadMe writes the file automatically the moment you publish, because it already owns your content and your build. A universal crawler like Firecrawl or an Apify Actor visits any URL, docs platform or not, and assembles the file from what it finds. A static site generator plugin, such as the community packages for Docusaurus and VitePress, writes the file at build time if you already run that framework and install one package.
A fourth option is a free, one-off web tool like Keploy's converter, which turns an existing sitemap.xml into a first draft in seconds, no account required. It stays useful for a quick check, but it will not keep itself current the way a platform or a plugin does on every publish.
Why the free plan quietly decides which generator fits
The catch with a hosted platform is that llms.txt is a side effect of moving your docs there, not a standalone purchase. Mintlify's Starter plan is free and includes the automatic file with 5 editor seats, but the next tier jumps hard once a team needs the Agent, Automations or preview deployments (see the pricing table); if that jump is the blocker, Mintlify alternatives covers the rest of the field. GitBook stays gentler: LLM optimizations, including llms.txt, llms-full.txt and a per-page Markdown version, ship on every plan including the free one, so a team that only wants the file never has to upgrade.
Fern's free plan is the most generous ceiling among the docs platforms: 10 team members and 1,000 pages before you pay anything, with the file rebuilt automatically on every change and a dashboard that breaks down which AI bot, OpenAI, Anthropic, Google or Perplexity among them, actually requested it. ReadMe puts LLMs.txt on its free Starter plan too, alongside an MCP server, then reserves team editing and its AI linter for the $250/mo Pro plan.
A plugin route costs nothing but a build step. Neither Docusaurus nor VitePress ships llms.txt by default: you install a free community package, docusaurus-plugin-llms or vitepress-plugin-llms, and it writes the file the next time you build. The VitePress plugin already runs in Vite, Vue.js, Vitest and Rolldown's own documentation, a stronger adoption signal than a fresh npm package with no real users behind it.
The crawler route bills by the page instead. Firecrawl's free plan covers 1,000 credits a month, roughly 1,000 pages scraped, then the next tier up adds 5,000 credits billed yearly (see the pricing table). Apify runs its official llms.txt Actor on your platform's compute credits rather than a per-page sticker: the free plan includes a small monthly credit allowance, and Starter raises that considerably. Neither charges for the Actor itself, only for the compute it consumes.
Key Features to Look For
Automatic regeneration on every publish (Essential)
Works on a site that isn't a docs platform (Essential)
Firecrawl and Apify crawl any URL, a marketing site, a blog or an app, and assemble the file from what they find there. The docs platforms and the framework plugins only cover pages already living inside them.
A free tier with a page or credit cap you can plan around (Essential)
Fern's free plan covers 1,000 pages, GitBook's free plan has no page cap at all, and Firecrawl's free plan covers roughly 1,000 pages scraped a month. Know which number applies before you assume free means unlimited.
llms-full.txt alongside the index file (Important)
Mintlify, GitBook, and both the Docusaurus and VitePress plugins also write an llms-full.txt bundling every page into one document, useful for a smaller site a model can read whole instead of link by link.
Traffic analytics broken down by AI bot (Important)
Fern's dashboard shows which LLM provider actually requested your llms.txt or Markdown pages, so you can see whether the file gets read at all. Most other generators here only confirm the file exists.
No signup for a single file (Nice to have)
Keploy's converter turns a sitemap.xml into an llms.txt in one visit, with no account and no card, which suits a one-off check more than an ongoing setup.
Serves Markdown instead of HTML once it detects a bot (Nice to have)
Fern automatically swaps in the Markdown version of a page when it detects an LLM crawler, which it says cuts the tokens that bot has to process by more than 90%. None of the other generators here do this by default.
What to settle before you pick one
Count your pages against the free cap. Fern stops the free plan at 1,000 pages, Firecrawl's free credits cover about 1,000 pages scraped a month, and GitBook's free plan does not cap pages, only sites and users.
Check whether the file has to update on every publish or only occasionally. A hosted platform rebuilds it live. A Docusaurus or VitePress plugin only updates on your next build, so a site that deploys weekly has a week-old file at worst.
Ask whether you need the file once or on a schedule. Keploy's converter and a one-off Firecrawl crawl suit a single audit. Apify's Actor suits a scheduled job across several sites, billed on compute credits rather than a flat fee.
Weigh analytics against a plain file. Fern is the only pick here that shows which AI bot actually reads the result. The rest confirm the file is live and correct, not whether anything is using it.
Evaluation Checklist
On Mintlify, publish one page and fetch yourdomain.com/llms.txt yourself to confirm the free Starter plan already lists it, with no separate dashboard step.
On Firecrawl, run a single crawl of your homepage and count the credits it consumes against the 1,000 included on the free plan before you plan a full-site run.
On Fern, check the dashboard for LLM bot traffic after a week live, since the free plan's real edge is knowing whether anything reads the file, not just that it exists.
On GitBook, confirm llms-full.txt renders on the free plan by appending /llms-full.txt to your docs URL, since GitBook lists this as included at every tier.
On Docusaurus or VitePress, install the community plugin in a branch first and diff the generated llms.txt against your sitemap, since neither ships this by default.
On Keploy's converter, paste your sitemap.xml and check the output lists every page you expect, since it works from that file alone and misses anything absent from it.
Pricing Overview
Free, no page cap
GitBook's free plan, plus the Docusaurus and VitePress plugins, which cost nothing but a build step.
$0/mo
Free up to a page or credit ceiling
$0/mo up to the cap
Paid platform or seat fee
Mintlify Pro, GitBook Premium and Ultimate, ReadMe Pro, and Firecrawl's paid credit tiers.
$16 to $450/mo
Pricing Comparison
| Tool | Published price | What that price buys | Billing |
|---|---|---|---|
Mintlify | Free (Starter), Pro $450/mo | Starter: automatic llms.txt and llms-full.txt, 5 editor seats. Pro adds unlimited seats and 10,000 AI credits/mo. | Per workspace, monthly |
Firecrawl | Free, then Hobby $16/mo | 1,000 credits/mo free (about 1,000 pages). Hobby adds 5,000 credits/mo, billed yearly. | Per credit, monthly or yearly |
Fern | Free forever | 10 team members, 1,000 pages, automatic llms.txt and llms-full.txt, bot-traffic analytics. | No platform fee up to the page cap |
Free, Premium $65/site/mo | LLM optimizations (llms.txt, llms-full.txt, per-page Markdown) on every plan, including free. | Per site plus $12/user on paid plans | |
Free (Starter), Pro $250/mo | Starter includes LLMs.txt and an MCP server free. Pro adds team editing and an AI linter. | Per project, Pro billed annually | |
Docusaurus | Free, open source | MIT license, no paid tier. llms.txt needs the free docusaurus-plugin-llms community package. | No platform fee |
Free, open source | MIT license. llms.txt needs the free vitepress-plugin-llms package, used by Vite and Vue's own docs. | No platform fee | |
Keploy | Free tool, no signup | Converts a sitemap.xml into an llms.txt in one visit. Keploy's core API testing product is a separate $19/user/mo plan. | Free tool, unrelated to the paid product |
Apify | Free ($5/mo credits) | Runs the official llms.txt Generator Actor on platform compute credits. Starter raises the allowance at $19/mo. | Usage-based compute units |
Prices verified on each vendor's pricing page on September 24, 2026, including Mintlify pricing and Firecrawl pricing. Docusaurus and VitePress are open source with no vendor to quote a price for the core framework.
Mistakes to Avoid
- ×
Assuming an AI crawler will actually read the finished llms.txt. Google Search Central has said the file is not required for its AI search surfaces, so treat it as one signal, not a guarantee.
- ×
Picking a hosted docs platform for the free llms.txt alone, then discovering the migration cost, in time and eventually in a pricier Pro tier, outweighs the file it was chosen for.
- ×
- ×
- ×
Forgetting that Docusaurus and VitePress plugins are community packages, not vendor features. Read the plugin's own changelog before a major version bump breaks the build.
Expert Tips
- →
Fetch your own llms.txt after every deploy for the first month, whichever generator you pick, and confirm new pages actually appear before you trust the automation.
- →
- →
- →
Check Fern's bot-traffic dashboard before assuming the file matters to your audience. If no AI bot has requested it in a month, your priority is probably elsewhere.
- →
Keep the file honest. List only the pages you want an AI model summarizing on your behalf, not every URL your sitemap happens to contain.
Red Flags to Watch For
- !
A Mintlify quote that assumes Pro at $450/mo is required for llms.txt. The file is on the free Starter plan; Pro buys the Agent and automations, not the file itself.
- !
A Firecrawl estimate that treats 1,000 credits as 1,000 pages of any size. An interactive scrape or a search costs more credits than a plain page fetch, so a JavaScript-heavy site burns the free tier faster.
- !
A Docusaurus or VitePress plan that assumes the file updates itself. Both need a rebuild to catch a new page, so a site publishing between deploys has a stale llms.txt until the next one.
- !
An Apify budget that prices only the Starter plan and ignores compute units. The Actor itself is free to run; the CU rate, from $0.20 down to $0.13 depending on plan, is the real meter.
- !
A Keploy estimate that expects the free converter to crawl your site. It reads your sitemap.xml only, so pages missing from that file never reach the output.
The Bottom Line
Choose Mintlify or GitBook when you already host docs there or are choosing a docs platform anyway: both write llms.txt and llms-full.txt automatically, free, with no separate tool to buy. Choose Firecrawl when your site isn't on either, since it crawls any URL and stays free up to 1,000 pages a month.
Choose Fern when you want the file plus proof it gets read, through its free bot-traffic dashboard. Choose ReadMe when the file needs to sit next to a full interactive API reference on a free plan. Choose Docusaurus or VitePress when you already run that framework and are willing to install one community plugin. Choose Keploy for a single file with no signup, and Apify when the job should run on a schedule across more than one site. Cite this: Toolradar, "Best llms.txt generators 2026", September 2026.
Frequently Asked Questions
What is the best llms.txt generator in 2026?
Mintlify and GitBook are the best defaults if you already host documentation there, because both write llms.txt and llms-full.txt automatically on the free plan. Firecrawl is the better pick for a site that isn't on a docs platform, free up to 1,000 pages scraped a month. Fern matches that free-forever deal and adds a dashboard showing which AI bot actually requested the file.
How much does an llms.txt generator cost?
Most of this list has a free tier that covers a small team or site: Fern to 1,000 pages, GitBook with no page cap at all, Firecrawl to about 1,000 pages scraped a month, and Mintlify and ReadMe on their free Starter plans. The bill starts once a team needs the paid AI features layered on top, or more pages than the free tier covers; the exact figures are in the pricing table above. Docusaurus and VitePress are open source with no vendor to bill, only a free community plugin to install.
Is there a free llms.txt generator?
Yes, most of the tools on this list have one. Keploy's converter needs no signup at all, working from your sitemap.xml. GitBook, Mintlify Starter, Fern, ReadMe Starter, Docusaurus and VitePress are all free, though Mintlify and ReadMe reserve their paid AI features for higher tiers, and Docusaurus and VitePress need a free community plugin installed before the file appears.
Do I need a docs platform to generate llms.txt?
No. Firecrawl and Apify's official Actor both crawl any website, docs platform or not, and assemble the file from what they find. A docs platform like Mintlify or GitBook is only the easiest route if you were already publishing there or planning to move.
Mintlify or Firecrawl for llms.txt?
Use Mintlify if your documentation already lives there or you are choosing a docs platform anyway, since the file is automatic and free on Starter. Use Firecrawl if your llms.txt needs to cover a marketing site, a blog, or any page outside a docs platform, since it crawls any URL directly.
Does llms.txt actually help my site get cited by AI models?
The evidence is mixed. Google Search Central has said the file is not required for its AI search surfaces, and crawl logs on some sites have shown gaps in how consistently major AI bots fetch it. Treat llms.txt as one signal among many, alongside clean Markdown pages and structured data, not a guaranteed citation.
What is the difference between llms.txt and llms-full.txt?
llms.txt is an index: a title, a summary, and a linked list of pages with short descriptions. llms-full.txt bundles the full content of those pages into one document, which suits a smaller site a model can read whole instead of following each link. Mintlify, GitBook, and the Docusaurus and VitePress plugins generate both files together.
Cite this page: Toolradar, "Best llms.txt Generators in 2026", updated September 2026, https://toolradar.com/guides/best-llms-txt-generators