llms.txt Guides · · 5 min read · By Mobilize Cloud

llms-full.txt is a single text file that holds the full content of your important pages, written out in Markdown, usually at yoursite.com/llms-full.txt. Where llms.txt is a short menu of links, llms-full.txt is the whole meal in one file.

Do you need one? Most small business and marketing sites don't. It's most useful for software documentation, where developers and AI coding tools want to load a whole set of docs at once. For a bakery, a law firm or a dental practice, a good llms.txt and clear web pages will do the job, and an llms-full.txt mostly adds something else to keep up to date.

What llms-full.txt is

An llms-full.txt file takes the pages you'd link to from llms.txt and puts their actual text into one long document. Instead of:

## Docs
- [Getting started](https://docs.tallybook.example/start): Create an account and send a first invoice

it contains the whole "Getting started" page, then the next page, and so on, usually with headings separating each one.

The idea is convenience. A tool that wants to understand your product can download one file and read everything, rather than visiting dozens of pages one by one and stripping out menus, footers and pop-ups.

Where the convention came from

It's worth knowing that llms-full.txt is a convention, not part of the core format. The llms.txt proposal published by Jeremy Howard of Answer.AI in September 2024 defines llms.txt itself: a title, a summary and sections of links. The proposal also suggests offering clean Markdown versions of individual pages. It doesn't define a file called llms-full.txt.

The name spread through documentation platforms. In November 2024, the docs platform Mintlify announced that it would automatically generate both /llms.txt and /llms-full.txt for the docs it hosts, describing llms-full.txt as all your docs content in one file. Other documentation tools and sites followed the same two-file pattern.

Because it's a convention rather than a written standard, there's no fixed format. Most files follow the llms.txt layout (a # title and a summary at the top) and then include page content under headings, but you'll see variations.

Who uses llms-full.txt

The sites that publish one are overwhelmingly developer documentation. Two examples that describe their files publicly:

  • Cloudflare says its llms-full.txt contains the full content of its documentation in a single file, for offline indexing, bulk vectorization or large-context models. Its main llms.txt is an index that links on to separate files for each product (Cloudflare's AI tooling page).
  • Pydantic, a popular Python library, offers both files and notes that its llms-full.txt "may be too large for some LLMs" (Pydantic's docs).

The common thread: a developer or an AI coding assistant wants the complete reference for a tool so it can answer detailed questions or write correct code. That's a real use. A large server-log study by Ahrefs in June 2026 found that Anthropic's coding tool, Claude Code, requested llms.txt files more than all AI search bots combined, which fits this picture (we cover that study in our review of the evidence).

As of October 2026, none of the major AI search assistants has said it reads llms-full.txt files from ordinary websites when answering questions. Google's guidance says Google Search doesn't use special AI text files at all.

The tradeoffs: size and upkeep

Size

Full files get big quickly. A documentation site with hundreds of pages can produce a file of several megabytes. That's often more than an AI model can take in at once, which is the warning Pydantic gives. Split files help: Cloudflare's approach of a separate full file per product keeps each one usable.

For comparison, our llms.txt validator warns when an llms.txt is over 1 MB and suggests moving long content into llms-full.txt. The short file should stay short; the full file is where length belongs, but it still has limits in practice.

Upkeep

This is the bigger cost for most businesses. An llms.txt lists links, so it only needs updating when pages are added, removed or renamed. An llms-full.txt copies your content, so it goes out of date every time you edit a page.

A stale copy is a real risk. If your prices, hours or policies change on your website but not in llms-full.txt, any tool reading the file gets the old version. Unless the file is regenerated automatically from your live content, someone has to remember to rebuild it after every change.

That's why llms-full.txt works best on platforms that build it for you from the same source as your pages, such as documentation tools that regenerate it on every publish.

Duplication and privacy

Everything in llms-full.txt is public. Before you publish one, make sure it doesn't pick up drafts, members-only pages, internal notes or staging links. Automatic generators that pull "all content" sometimes include more than you meant to share.

Do you need one? A quick guide

Your siteOur suggestion
Software product with developer docs or an APIWorth having, ideally generated automatically by your docs platform on every publish.
Knowledge base or help center with many articlesConsider it if it can be generated automatically. Split it by topic if it gets large.
Local business, agency or professional services siteSkip it. Put your effort into a good llms.txt and clear pages.
Online shopUsually skip it. Product details change too often to copy into a static file.
Blog or publisherUsually skip it. Your articles are already readable pages, and copying them all creates a very large file.

If you do publish one

  1. Start with a solid llms.txt. The full file is an extra, not a replacement. Our anatomy of a great llms.txt file shows what the short file should look like.
  2. Generate it, don't hand-copy it. Use your docs platform, a plugin or a build step that rebuilds it from your live content.
  3. Keep it focused. Include the pages you'd list in llms.txt, not every archive, tag page and old post.
  4. Serve it as plain text at /llms-full.txt, the same way as your llms.txt.
  5. Link to it from llms.txt if you want tools to find it, for example in your Optional section.
  6. Check it after big changes to your site, such as a redesign or migration.

When you check a domain with our validator, the technical details also show whether an llms-full.txt was found, with its size, title and number of links. Sites listed in our directory that publish one get a link to it on their listing.

Bottom line: llms-full.txt is a useful convention for documentation-heavy sites, especially when a docs platform builds it automatically. For most business websites, it's extra upkeep with little evidence of benefit. Get your llms.txt right first, and add a full file only if you can keep it current without thinking about it.

Is your llms.txt working?

Check any site for free and get plain-English fixes in seconds.

Keep reading