Free tool

Free llms-full.txt Generator

An llms-full.txt file is the content itself: one Markdown document holding the readable text of the pages you choose, in a simple format of a heading and source address per page. Scan your site, pick the sections that matter, and download the file, with a matching llms.txt if you want one. No payment, no account.

Build the file

Last updated

Generate your llms-full.txt

Two steps. First we scan the site and show you what is there. Then you choose the sections to include and how much of each page to keep.

Find the pages

We read your sitemap if there is one, or the links on your homepage.

Publish it as /llms-full.txt next to your llms.txt, and link to it from there.

Your llms-full.txt

You can edit files up to 1 MB here. Copy, Download and Validate use your edited version; the validator accepts files up to 512 KB.

How does the llms-full.txt generator work?

1

Scan

We read your sitemap, or the links on your homepage, and sort every URL into sections by the first part of its path. Media files, feeds, archives, search results, login, cart and legal pages are set aside.

2

Choose

Untick the sections you do not want, pick full text or summaries, and set a page limit. The estimate updates as you go so the file does not end up too large to use.

3

Generate

We fetch the chosen pages one at a time, keep the main content, convert it to Markdown and join the pages into one file. Pages your robots.txt disallows are skipped.

Which file do you actually need?

Publish llms.txt first and treat llms-full.txt as an addition, not a replacement. The index tells a model where to look. The full file answers the question without any further requests.

<code>llms.txt</code><code>llms-full.txt</code>
ContainsLinks plus one-line descriptionsThe readable text of each page
Typical size2 to 10 KB100 KB to a few MB
Answers“Where should I look?”“What does it say?”
Rebuild whenYour site structure changesAny page content changes
Good fitEvery siteDocs, APIs, knowledge bases, policies

The trade-off is staleness. A link index stays accurate for months; a full-text copy is out of date the moment you edit a page. If you cannot rebuild it automatically, keep it small and limit it to pages that rarely change. There is more detail in llms.txt vs llms-full.txt.

Full text or summaries?

Full text keeps up to about 20,000 characters of each page, roughly 3,000 words, cut at a paragraph break. Choose it for documentation, help centres and policies, where the exact wording matters.

Summaries keep each page's description, a list of its headings and its opening 1,200 characters. A 50-page summary file is usually 60 to 100 KB, small enough for almost any tool to load. Choose it when you want a model to know what every page covers without carrying the whole site.

Watch the size. A file larger than a model’s context window cannot be loaded at all, and most tools give up rather than trim it sensibly. Under about 500 KB is a good ceiling. The estimate shows where you are before you generate.

What does the generator keep from each page?

It keeps the part of the page a reader came for and drops the rest. It looks for the main content in this order: the page’s <main> element, a single <article>, a block whose name marks it as content (such as content or post), and only then the whole body. That content is converted to Markdown.

Kept, as MarkdownRemoved
Headings, paragraphs and quotesNavigation, headers, footers and sidebars
Bulleted and numbered listsScripts, styles, forms, buttons and dialogs
TablesEmbedded frames, video, audio and canvas
Code blocks and inline codeImages (a text file cannot carry them)
Links, rewritten as full URLsComments and hidden templates

Unusual layouts can still let a menu or a cookie notice through, so read the result before you publish it. You can edit it in the page first.

What does an llms-full.txt file look like?

One H1 for the site, a one-line summary, then each page as an H2 with its URL underneath and its content in Markdown. Navigation, footers, cookie banners and scripts are removed.

llms-full.txt

# Riverbend Ceramics

> Full-content companion to https://example.com/llms.txt. Generated 2026-10-07 from https://example.com/sitemap.xml: 2 pages, full text.

## Caring for stoneware
Source: https://example.com/guides/care

> Washing, thermal shock and repairing chips in hand-thrown stoneware.

Stoneware is fired above 1200°C, which makes it far less porous
than earthenware, so it can go in the dishwasher.

### Thermal shock

- Let it warm up before it goes in a hot oven
- Never move it straight from the freezer to the hob

## Glaze safety
Source: https://example.com/guides/glaze-safety

Every glaze we use is tested to the EU food-contact limits...

Where do you publish llms-full.txt?

  1. Upload it to your domain root, next to llms.txt, so it loads at https://yourdomain.com/llms-full.txt. It goes in the same place as llms.txt on every platform; the platform table on the homepage shows where that is, and there are guides for WordPress, Shopify and Next.js.
  2. Serve it as plain text, text/plain or text/markdown, not as an HTML page.
  3. Link to it from your llms.txt so a model reading the index knows the long form exists, for example - [Full content](https://yourdomain.com/llms-full.txt): The text of every page in one file. The matching llms.txt this tool offers already lists the same pages.
  4. Check it. The validator judges an llms-full.txt on its headings and how it is served.

Since llms.txt V2, a site can also offer a Markdown version of each individual page, which suits large sites better than one huge file.

Frequently asked questions

Is the full generator free too?

Yes. There is no account, no payment and no email to give, and you see the whole file before you download it. A free run reads up to 50 pages, with 3 runs a day across the generators. Larger runs are planned for paid plans; the free tool stays free.

Can I regenerate it after I update my site?

Yes, as often as your free runs allow. A full-text file goes out of date the moment a page changes, so rebuild it after any edit that matters, or switch to Summaries, which change less often.

My site has hundreds of pages. What should I do?

Choose, rather than include everything. Untick sections such as blog archives, keep the pages people ask about most (docs, pricing, policies, help), and use Summaries for the rest. For a very large site, a Markdown version of each page, which llms.txt V2 allows, usually serves models better than one huge file.

Why was a page left out?

The scan sets aside media files, feeds, pagination, search results, tag, category and author archives, login and cart pages, and legal pages. During generation, pages the site’s robots.txt disallows are skipped, and so are pages that are not HTML. Open the “skipped” list under the result to see each reason.

Why is my file so large?

Full text adds up quickly. Switch to Summaries, lower the page limit, or untick sections such as a long blog archive.

Does it strip navigation and boilerplate?

It keeps the page’s main content region and removes navigation, headers, footers, sidebars, forms and scripts. Unusual layouts can still leak a menu, so read the result before you publish it.

Is anything stored?

No. Pages are fetched, converted and discarded when the request ends, and the finished file is sent only to your browser. See the privacy page.

What are the size limits?

Two limits, for different reasons. You can edit a result in the page up to 1 MB; above that it is shown read-only because browsers slow down, but Copy and Download still give you the whole file. The validator accepts files up to 512 KB. Sizes are counted in bytes, so text with accented letters or other scripts reaches the limits sooner than plain English.