Skip to content
Guide
General

Pricing

Detailed information about LlamaParse credit pricing and usage rates for parsing, indexing, extraction, classification, and split services.

All features are priced using credits. Most document processing is billed per page, audio per minute, and storage per GB per day. Extract’s Max effort option is priced by the processing each document needs, with the page price as the minimum. Credits vary by configuration and whether files are cached.


Credits cost $1.50 per 1,000 on Pay as you go and $1.25 per 1,000 on Pro. Enterprise rates are set by contract. See Billing and Usage for plans, credit packs, and auto-reload.

In the v2 API, parsing uses a simplified tier-based system. Choose a tier and the platform handles model selection automatically.

Tier Credits per Page
Fast 1
Cost-effective 3
Agentic 10
Agentic Plus 25

Additional Configs:

  • Layout extraction: +3 credits per page (can be added to any tier)
  • Enriched forms output (Beta): included in the page price on Agentic and Agentic Plus; +10 credits per page containing a form on Cost-effective (details; not available on Fast)
  • Spreadsheet: 1 credit per sheet
  • Audio: 3 credits per minute
  • Markdown (.md): the file itself bills as a single Fast page (1 credit) regardless of length, plus 1 page at the job’s tier rate for each successfully extracted inline image (base64 data URI or remote URL; relative/local paths are never extracted). Fast-tier jobs don’t extract inline images, so a .md file on Fast always bills exactly 1 credit.

Action Credits
Exported page 2 per page
Retrieval query 1 per query
Chat turn 100 per turn

These charges are on top of parsing and document storage costs.


Retained files — files stored without an expiration — are billed daily on each project’s total stored size:

Item Credits
Retained file storage 100 per GB per day (0.1 per MB)

LlamaCloud snapshots each project’s retained storage once a day and charges it at the rate above. Ephemeral files — files uploaded with an expiration or retention period, including files in ephemeral directories — are never charged for storage.

Retained storage is also capped per project by plan tier; see the plan comparison for the limits and what happens when a project reaches them. To stop paying for a file, delete it, or upload files ephemerally when you don’t need them retained.


In the v2 API, total credits per page are the extract tier plus the parse tier.

The default price includes both steps:

Extract tier Extract credits/page Default parse tier Parse credits/page Default total
Agentic Plus 50 Agentic 10 60
Agentic 15 Agentic 10 25
Cost-effective 5 Cost-effective 3 8

You can choose a different parse tier with parse_tier in the configuration (in the Extract playground, under Advanced settings → Processing). Its cost is added to the extract tier:

Parse tier Credits/page
Agentic Plus 25
Agentic 10
Cost-effective 3
Fast 1

For text files or files already parsed by LlamaParse, only the extract tier applies. Text files (md, txt, csv, html) use 600 tokens as one page.

Max effort: Charges vary with how much processing each document needs. The Agentic Plus page price is the minimum. Any Parse charge is separate. See Max effort for configuration.

Turbo: Turbo prepares documents itself instead of running a separate Parse step, so it has no parse tier and one all-in rate:

Extract tier Credits/page
Turbo 35

Because Turbo skips parsing, it produces no parse output and accepts no parse tier or parse configuration — those settings are ignored if sent. It does not produce granular bounding boxes. See Tiers for feature availability.

Spreadsheet mode: Spreadsheet mode reads an Excel or CSV workbook directly. It is available on Cost-effective, Agentic, and Agentic Plus. Each tier uses its extract rate with no separate Parse charge:

Extract tier Credits per billed page
Cost-effective 5
Agentic 15
Agentic Plus 50

A CSV is billed as a workbook rather than under the text-file rule above. A workbook has no fixed pages, so the billed page count is 10 + ceil(non_empty_cells / 1000), independent of the number of worksheets. A workbook with 1–1,000 non-empty cells bills 11 pages: 55 credits on Cost-effective, 165 on Agentic, or 550 on Agentic Plus. Read metadata.usage.num_pages_billed from the completed job for the exact count charged.

Cost-effective and Agentic require extract version 2.1 or later for spreadsheet mode.


Total credits per page are the split charge plus the parse tier.

Mode Split credits/page Default parse tier Parse credits/page Default total
Default 3 Fast 1 4

A different parse tier (parse_tier or parse_config_id) is charged at that tier’s Parse price. A job that reuses a completed Parse job or a cached parse pays only the split charge.


Mode Credits per Page
Fast 1
Multimodal 2

  1. Use caching — Parsed files are cached for 48 hours. Re-parsing the same file within that window is free.
  2. Choose the right tier — Start with Cost-effective (3 credits) for initial testing. Only move to Agentic (10) or Agentic Plus (25) when document complexity requires it. Fast (1 credit) runs no AI model, so it suits plain-text documents only.
  3. Use page ranges — Parse only the pages you need instead of entire documents. Specify target_pages to avoid processing irrelevant content.
  1. Leverage extract-only pricing — If a file was previously parsed, subsequent extractions cost less (extract-only rates apply). Parse once, extract many times.
  2. Pre-filter with Classify — Use Classify (1-2 credits/page) to filter documents before running more expensive Parse or Extract jobs.
  3. Batch strategically — Group similar documents in a single job when possible rather than submitting many small requests.
Note for AI agents: this documentation is built for programmatic access. - Overview of all docs: https://developers.llamaindex.ai/llms.txt - Any page is available as raw Markdown by appending index.md to its URL — e.g. https://developers.llamaindex.ai/llamaparse/parse/getting_started/index.md - Agent-friendly REST search APIs live under https://developers.llamaindex.ai/api/ — search (BM25 full-text), grep (regex), read (fetch a page), and list (browse the doc tree). See https://developers.llamaindex.ai/llms.txt for parameters. - A hosted documentation MCP server is available at https://developers.llamaindex.ai/mcp. If you support MCP, you can ask the user to install it for browsing these docs directly (an alternative to the REST API). Setup: https://developers.llamaindex.ai/for-agents/mcp/ - Other LlamaIndex tooling for agents — the LlamaParse Platform MCP server, agent skills and plugins, and the n8n node — is mapped at https://developers.llamaindex.ai/for-agents/