# What is llms-full.txt and how it differs from llms.txt

> llms-full.txt is the whole text of the documentation in one file. How it differs from llms.txt, who publishes it, how big it gets and when it is not needed

Page: https://llms-full-txt.ru/en/guides/llms-full-txt/
Site index: https://llms-full-txt.ru/en/llms.txt

`llms-full.txt` is a file that holds the whole text of a site's documentation in sequence, as Markdown. `llms.txt` gives links, `llms-full.txt` gives the content right away.

The file is not in the proposal: neither in the first edition nor in the second. It is a practice introduced by documentation platforms, and it stuck.

an ecosystem convention, not part of the proposal
## An index and the full text

- Two files, two jobs
- llms.txt
- where to go
- A name, a summary and lists of links
- Small: fits into a model context as a whole
- Described in the proposal
- For details the agent follows the links
- llms-full.txt
- everything at once
- The text of all pages in sequence
- Large: from hundreds of kilobytes to tens of megabytes
- Not part of the proposal
- Easy to load into an assistant in one step

## How big these files get

- 67 MB
- the full text of the Cloudflare docs: 40.9 MB
- the full text of the Anthropic docs: 8.5 MB
- the full text of the OpenAI docs

A file of tens of megabytes does not fit into any model's context as a whole. It is used differently: loaded into a tool that splits the text into chunks and searches them.

Hence a practical rule: the smaller the documentation, the more useful `llms-full.txt` is. For a small project a file of a hundred kilobytes can be handed to an assistant whole, and it will know everything. For huge documentation the file becomes an archive, and the index of links does the work.

## Who publishes it

Among the sites checked on October 3, 2026:

| Both files | llms.txt only |
|---|---|
| OpenAI, Anthropic, Cloudflare, Vercel, Supabase, LangChain, Perplexity, Vue, Svelte, Docker, Gravity UI | Stripe, Next.js, React, GitHub Docs, Yoast, Wix, WordPress.org |

Stripe and GitHub do without the full file and lose nothing: they have the index and Markdown versions of pages. `llms-full.txt` is optional.

The full list with the check date: [the adoption registry](https://llms-full-txt.ru/en/reference/adoption/).

## When the file is justified

- The documentation fits into a few hundred kilobytes.
- Users load it into an assistant whole to ask questions.
- The documentation platform builds the file itself, so nobody maintains it by hand.

## When it is not needed

- The site has no documentation: it is a store, a blog, a company site.
- There is so much text that nobody can read the file as a whole.
- The file would be assembled by hand and would go stale.

## And llms-small.txt

Another name that is not in the proposal. It stands for a shortened version of the full file: the same text without examples and secondary sections. It is rarer, and there are no shared rules for it.

## What is known

**Confirmed**

- Large documentation sites publish the file.
- According to Mintlify, over one week in 2025 `llms-full.txt` was requested more often than `llms.txt`: a median of 79 against 14 requests. The sample is 25 companies, and the source is an interested party.

**Not proven**

- That the file affects search or AI answers.
- That a correct file size exists: there are no norms.

**What it does not mean**

- The domain name of this site does not make the file a standard. We explain a practice; we do not declare a norm.

## Next

- How the index is built: [the llms.txt format](https://llms-full-txt.ru/en/specification/format/).
- How to serve pages as Markdown without one big file: [Markdown versions of pages](https://llms-full-txt.ru/en/guides/markdown-pages/).
- Which tools build both files: [generators](https://llms-full-txt.ru/en/tools/generators/).