Do You Need Both llms.txt and llms-full.txt? A Complete Guide

When I first added an llms.txt file to a client's documentation site, their immediate question was: "Do we also need to create an llms-full.txt file? What's the difference?"

It's a common question. With two different file formats in the llms.txt ecosystem, it's important to understand their distinct purposes and when you might need one, the other, or both.

This guide assumes you've already decided these files are worth creating—which, realistically, they are if you maintain developer documentation, an API, or a product that AI coding assistants need to understand. If you're still weighing whether they're worth the effort at all, our evidence-based look at whether llms.txt actually works in 2026 is the better place to start. With that settled, I'll break down the differences between llms.txt and llms-full.txt, how they complement each other, and help you decide which approach is right for your site.

The Key Differences

Before diving into details, here's a quick comparison of these two file types:

Now, let's explore each file in depth.

Understanding llms.txt: The Navigation File

An llms.txt file serves as a navigation guide for AI language models. It provides a concise summary of your website or project, a structured hierarchy of important content, links to markdown files with more detailed information, and suggestions for which content is essential versus optional.

Here's a typical example:

# Project Documentation

> An open-source framework for building responsive web applications.

This framework provides components, utilities, and patterns for creating modern web experiences.

## Getting Started

- [Installation](https://example.com/docs/installation.md): How to install and set up the framework
- [Quick Start](https://example.com/docs/quickstart.md): Build your first application

## Components

- [Button](https://example.com/docs/components/button.md): Button component documentation
- [Form](https://example.com/docs/components/form.md): Form component documentation

## Optional

- [Contributing](https://example.com/docs/contributing.md): How to contribute to the project
- [Change Log](https://example.com/docs/changelog.md): Version history

The llms.txt file shines when an AI needs to quickly understand what your project is about, find specific information, conserve context window space, or when you want to control exactly which resources the AI accesses. Think of llms.txt as the map that helps AI systems navigate your content ecosystem. Understanding how LLMs process these navigation files can help you structure yours more effectively.

Understanding llms-full.txt

While llms.txt provides structure and navigation, llms-full.txt contains the actual complete content. It includes all the important documentation in a single file, with formatted markdown that preserves the structure and hierarchy, including the full text of linked pages from your llms.txt.

Here's a simplified example of what llms-full.txt might look like:

# Project Documentation

An open-source framework for building responsive web applications.

This framework provides components, utilities, and patterns for creating modern web experiences.

## Getting Started

### Installation

To install the framework, run:

npm install @example/framework

Make sure you have Node.js version 14 or higher installed.

### Quick Start

Create your first application by following these steps:

1. Initialize a new project
2. Add dependencies
3. Configure settings
4. Build your components

...and so on with all the content from your documentation...

The llms-full.txt file is valuable when an AI needs complete information to provide detailed help, when sharing code examples and implementation details, as an offline reference, or when you want to ensure the AI has all relevant information without needing to fetch multiple files. Think of llms-full.txt as the encyclopedia that gives AI systems full knowledge of your content.

Choosing What You Need

The short answer: It depends on your use case, but for most documentation sites, having both provides the best experience.

When Both Files Make Sense

Having both files works well when your documentation is extensive and wouldn't fit in a single context window, when you serve different AI use cases (some needing navigation, others needing full content), or when you want to provide the best possible experience. This is the approach taken by many developer tools and documentation sites. Looking at how companies like Stripe, Zapier, and Cloudflare implement both files shows the value of this dual approach.

Major companies provide both files for flexibility. Anthropic's Claude documentation, Zapier, and Cloudflare all maintain both llms.txt and llms-full.txt versions to give AI systems maximum flexibility in how they access information.

When One File Is Enough

You might only need llms.txt when your content is already well-structured online with each linked .md file easily accessible, your documentation is relatively small, or you're just getting started with the standard.

Conversely, llms-full.txt alone might suffice when your documentation is concise enough to fit in one file, you have a simple documentation structure, or your content changes infrequently.

Practical Implementation

If you decide to implement both files, there are some practical matters to consider.

One challenge is keeping both files in sync. You might want to create an automated process that generates both files from your source content, update the files as part of your build process, or implement versioning to ensure both files reflect the same documentation version.

The implementation approach varies by platform. If you're using WordPress, most plugins automatically generate both files. For Next.js or React applications, you can set up dynamic generation to keep both files in sync. Check out our platform-specific guides on adding llms.txt to WordPress or implementing it in Next.js and React for detailed instructions.

It's also important to ensure both files are properly accessible. Both should be at the root of your domain, served with the correct MIME types (text/markdown or text/plain), and your llms.txt should include a link to llms-full.txt. You can validate your llms.txt to verify your implementation.

Real-World Applications

Different organizations implement these files in various ways based on their needs.

• A code editor might use llms.txt for a structured overview with links to sections on installation, features, and API documentation, while its llms-full.txt contains complete documentation including all code examples and tutorials.
• A SaaS company might use llms.txt to link to product explanations, pricing, and support information, with llms-full.txt providing detailed information about their offerings, integration guides, and FAQs.
• An open-source project might include llms.txt with an overview of the project structure, installation, and contributing guidelines, while llms-full.txt contains the complete README, contribution guidelines, API documentation, and examples.

Browse our directory of sites using llms.txt to see how different types of organizations structure their implementations.

How AI Systems Use These Files

The clearest, best-documented use of these files is in AI coding assistants and agents. Development environments like Cursor or GitHub Copilot can be pointed at your documentation and will pull in llms-full.txt for complete context when helping with coding tasks—this is exactly the scenario the standard was designed for. Agent tooling, including MCP servers that expose llms.txt to IDEs, uses llms.txt for orientation and llms-full.txt for deeper retrieval.

General-purpose chatbots are a different story. An assistant like Claude or ChatGPT can make good use of these files when a user or tool provides them directly, but you generally shouldn't expect a chatbot to discover and fetch your llms.txt on its own during a normal web search. As covered in our 2026 state-of-the-standard analysis, that kind of automatic, unprompted use isn't how most AI systems behave today—which is why the real payoff for both files is in the agent and coding-tool context, not in general AI search.

Creating Your Files

If you're ready to create either or both files, we have detailed guides to help:

• How to Create Your First llms.txt File - Step-by-step guide to creating the navigation file
• How to Create an llms-full.txt File - Detailed instructions for the full content version

Both guides include examples, best practices, and tips for maintaining your files over time.

Best Practices

If you implement both files, consider these approaches.

In your llms.txt, include a cross-reference link to llms-full.txt for AI systems that prefer the complete approach:

# My Project

> A brief description of my project.

For complete documentation in a single file, see [Full Documentation](https://example.com/llms-full.txt).

## Documentation
...

Keep information consistent across both files and ensure they reflect the same version of your documentation. Put important information first to maximize the value of limited context windows, use consistent heading levels and formatting, and update both files regularly as your documentation evolves.

Conclusion

While llms.txt and llms-full.txt serve different purposes, they complement each other in creating an AI-friendly content ecosystem. The navigation-focused llms.txt helps AI coding assistants and agents understand your content structure, while llms-full.txt provides the complete information they need to work with your product accurately.

For most sites with substantial developer documentation, implementing both files provides the best experience for the AI tools that consume them. However, depending on your specific situation, one file type might be sufficient—and if your content is small and your linked pages are already clean and accessible, llms.txt alone is a perfectly reasonable starting point.

As the standard continues to evolve, the patterns established by leading developer-tools companies are the most reliable guide. Following those conventions and using our tools to validate your implementation will set you up well.