Export Formats

EpicContext's core principle is store once, export everywhere. Your structured content can be exported in multiple formats optimized for different consumers.

Available Formats

Markdown

Human-readable documentation generated from your blocks. Great for:

• Sharing with team members who don't use EpicContext
• Including in repositories as documentation
• Generating PDFs or static sites

Each block type has a markdown template that renders its fields in a clean, readable format.

llms.txt

A specialized format optimized for Large Language Model consumption. The llms.txt format:

• Uses structured sections with clear delimiters
• Includes relationship metadata between blocks
• Prioritizes information density over readability
• Follows the emerging llms.txt standard

# EpicContext Project: My Product
> Product context documentation

## Brand
### Brand Positioning
Target audience: ...
Value proposition: ...

JSON API

Full structured access to your blocks via the REST API. Use this for:

• Building custom integrations
• Syncing with other tools
• Programmatic content updates

CONTEXT Folder

A file-based export that creates a structured folder of markdown files, designed to live in your code repository:

CONTEXT/
├── AI-GUIDE.md          # Auto-generated navigation for AI agents
├── brand/
│   ├── brand-overview.md
│   └── tone-of-voice.md
├── product/
│   └── features/
│       └── my-feature.md
├── users/
│   └── personas/
│       └── primary-user.md
└── technical/
    └── technology-stack.md

Choosing the Right Format

Bidirectional Sync

The CONTEXT folder supports bidirectional sync — you can edit markdown files locally and import changes back into EpicContext:

1. Export your project to a CONTEXT folder
2. Edit files locally (or let AI agents edit them)
3. Import changes back via Settings > Export/Import

This enables a workflow where AI agents can both read and contribute to your product context.