llms.txt is a proposed convention for a Markdown file at your site's root (/llms.txt) that gives large language models a concise, curated map of your most important pages — like robots.txt or sitemap.xml, but for LLMs. It links key pages (ideally clean Markdown versions) with short descriptions so an assistant can find what matters without crawling full HTML.

What is the llms.txt format?

One H1 title, then a blockquote summary, then optional heading-free intro prose, then any number of H2 sections each containing a Markdown bullet list of links in the form - [name](url): optional note. A special "## Optional" section marks links an LLM may skip for a shorter context. Only the H1 is strictly required.

Where do I put the llms.txt file?

Publish it at the root of your domain — yoursite.com/llms.txt — as a plain-text/Markdown file, the same way you'd serve robots.txt. Generate it here, download it, and drop it in your site's public/static root.

Do LLMs actually read llms.txt?

It's an emerging, community-driven standard rather than a ratified spec, and support among model vendors is inconsistent — there's no guarantee any given LLM reads it. Treat it as low-cost, forward-looking hygiene: it can't hurt, adoption is growing, and it doubles as a clean human-readable index of your key pages.

llms.txt

llms.txt Generator

Produce a spec-compliant llms.txt file from a short form, with live preview, copy, and download.

Updated Jul 5, 2026FreeNo signup

Site title

One-line summary

Intro paragraph (optional)

Optional section (secondary links)

Live preview — /llms.txt

# Acme Widgets

> Acme Widgets is a TypeScript SDK for building configurable UI widgets with type-safe schemas and zero client-side runtime dependencies.

## Docs

- [Quick start](https://acme.example/docs/quickstart.md): Render your first widget in five minutes
- [Schema guide](https://acme.example/docs/schemas.md): Define, compose, and validate widget schemas

## Optional

- [Changelog](https://acme.example/docs/changelog.md): Release history and migration notes

Save this as llms.txt and publish it at yoursite.com/llms.txt.

TL;DR

Fill in your site's key pages and get a ready-to-publish llms.txt — the emerging convention for telling LLMs which of your pages matter. It's a Markdown file with an H1 title, a > summary, and ## Section lists of [name](url): note links. Download it and drop it at yoursite.com/llms.txt. The format explainer is below.

What is llms.txt?

Updated Jul 5, 2026

llms.txt is a proposed convention for a Markdown file served at a site's root (/llms.txt) that gives large language models a concise, curated map of your most important pages — much like robots.txt or sitemap.xml do for search crawlers. It exists because LLMs have limited context windows and struggle to extract signal from full HTML pages, so you hand-author a short list of key pages (ideally linking to clean Markdown versions) with brief descriptions. It's an emerging, community-driven standard — low-cost, forward-looking hygiene, not a guaranteed ingestion mechanism.

llms.txt structure
Part	What it is
# Title (H1)	Exactly one — the project or site name. The only required element.
> Summary	A blockquote right after the title. Strongly recommended.
Intro prose	Optional free-form paragraphs — but no headings before the first H2.
## Section	H2 heading + a bulleted list of [name](url): optional note links.
## Optional	A reserved section whose links an LLM may skip for a shorter context.

Example llms.txt

# Acme Widgets

> Acme Widgets is a TypeScript SDK for building configurable UI widgets with type-safe schemas and zero client-side runtime dependencies.

## Docs

- [Quick start](https://acme.example/docs/quickstart.md): Render your first widget in five minutes
- [Schema guide](https://acme.example/docs/schemas.md): Define, compose, and validate widget schemas
- [Component reference](https://acme.example/docs/components.md): Every built-in widget and its props

## Optional

- [Changelog](https://acme.example/docs/changelog.md): Release history and migration notes

How it works

The generator emits exactly the format from llmstxt.org: an H1 title, a blockquote summary, optional intro prose (with any accidental headings stripped, since nothing between the summary and the first H2 may be a heading), then your ## sections as Markdown link lists, and a ## Optional section last if you add secondary links.

Everything runs in your browser — nothing is uploaded. llms.txt is a proposed standard; the output tracks the current spec at llmstxt.org, which may evolve.

Sources

llmstxt.org — the /llms.txt proposal

FAQ

What is llms.txt?: llms.txt is a proposed convention for a Markdown file at your site's root (/llms.txt) that gives large language models a concise, curated map of your most important pages — like robots.txt or sitemap.xml, but for LLMs. It links key pages (ideally clean Markdown versions) with short descriptions so an assistant can find what matters without crawling full HTML.
What is the llms.txt format?: One H1 title, then a blockquote summary, then optional heading-free intro prose, then any number of H2 sections each containing a Markdown bullet list of links in the form - [name](url): optional note. A special "## Optional" section marks links an LLM may skip for a shorter context. Only the H1 is strictly required.
Where do I put the llms.txt file?: Publish it at the root of your domain — yoursite.com/llms.txt — as a plain-text/Markdown file, the same way you'd serve robots.txt. Generate it here, download it, and drop it in your site's public/static root.
Do LLMs actually read llms.txt?: It's an emerging, community-driven standard rather than a ratified spec, and support among model vendors is inconsistent — there's no guarantee any given LLM reads it. Treat it as low-cost, forward-looking hygiene: it can't hurt, adoption is growing, and it doubles as a clean human-readable index of your key pages.