# Data extraction modes Source: https://www.digiparser.com/docs/guides/parsers/parser-settings/data-extraction-modes ParsersParser Settings # Data extraction modes Understand Fast, Accurate, and Critical modes, when to use each one, and how they impact speed, quality, and credits. Copy MarkdownOpen # [Data extraction modes](#data-extraction-modes) Feedback **Data extraction mode** controls how DigiParser balances speed and extraction quality for your parser. Feedback You can choose: Feedback * **Fast** - prioritizes speed * **Accurate** - balanced speed and quality * **Critical** - highest precision for business-critical documents ## [Where to find it](#where-to-find-it) Feedback 1. Open your parser and go to **Settings -> Parser Settings**. 2. Scroll to **Parsing Configuration**. 3. Find **Data extraction mode**. 4. Choose **Fast**, **Accurate**, or **Critical**. 5. Click **Save Parser**. app.digiparser.com![Parsing Configuration showing Data extraction mode dropdown with Fast, Accurate, and Critical options](https://documents.digiparser.com/docs/screenshots/2026-07-23/parser-settings-processing-controls.png?sig=88dee9493cc32581aba85341e936e250b59243004ee0ff90637f136c7753d1a2) ## [What each mode does](#what-each-mode-does) ### [Fast](#fast) Feedback Choose **Fast** when speed matters most. Feedback * Good for high-volume daily processing * Useful when documents are well-structured and consistent * Best when your team accepts slightly lower extraction quality in exchange for faster results ### [Accurate](#accurate) Feedback Choose **Accurate** when you want a strong balance of quality and speed. Feedback * Best default for most teams * Good for mixed document quality * Useful when you want dependable extraction without max-cost settings ### [Critical](#critical) Feedback Choose **Critical** when precision is more important than speed. Feedback * Best for high-risk or high-value documents * Useful when mistakes are expensive (for example, financial totals or compliance-sensitive data) * Ideal for final checks, exception batches, or critical workflows ## [Credit impact](#credit-impact) Feedback Based on current parser credit logic: Feedback * **Fast**: **1 credit per page** (standard processing) * **Accurate**: **1 credit per page** (standard processing) * **Critical**: **+2 credits per page** on top of standard processing (**3 credits per page** total) Feedback If you also enable confidence scores, those add extra credits as documented in [Credits and Billing](/docs/guides/troubleshooting/credits-and-billing). ## [How to choose a mode](#how-to-choose-a-mode) Feedback Use this simple approach: Feedback 1. Start with **Accurate**. 2. If your throughput is high and extraction quality is already stable, try **Fast**. 3. For critical document sets, switch to **Critical**. 4. Review a sample batch after each mode change before rolling it out widely. ## [Suggested mode by use case](#suggested-mode-by-use-case) Use case Recommended mode Why Daily operational documents with clean layouts **Fast** or **Accurate** Keeps processing moving quickly Mixed vendor formats with normal business risk **Accurate** Good balance for most teams Financial approvals, legal-sensitive records, or high-cost errors **Critical** Highest precision where mistakes are costly ## [How mode changes apply](#how-mode-changes-apply) Feedback After you click **Save Parser**: Feedback * The new mode applies to new documents processed by that parser * Existing processed documents keep prior results unless re-processed * You can change mode any time based on workload or quality needs ## [Best practices](#best-practices) Feedback * **Use Accurate as your baseline**: It is the safest default for most non-technical teams. * **Use Critical selectively**: Reserve it for important document types or final verification steps. * **Track quality by document type**: One mode may work differently across vendors and formats. * **Run sample checks after changes**: Process a small batch and review key fields before full rollout. * **Align mode to business impact**: Higher-risk workflows should use stricter settings. ## [Common questions](#common-questions) ### [Is Accurate the same as Critical?](#is-accurate-the-same-as-critical) Feedback No. **Accurate** is balanced for everyday use, while **Critical** is designed for maximum precision and higher credit cost. ### [Should I use Fast everywhere to save time?](#should-i-use-fast-everywhere-to-save-time) Feedback Only if extraction quality remains good on your real documents. If review time increases because of corrections, **Accurate** may be better overall. ### [Can I change the mode later?](#can-i-change-the-mode-later) Feedback Yes. You can change it at any time in **Parser Settings**, then click **Save Parser**. ## [Next steps](#next-steps) Feedback * [Advanced Table Extraction](/docs/guides/parsers/parser-settings/advanced-table-extraction) - Improve results for long and complex tables * [Confidence scores](/docs/guides/parsers/parser-settings/confidence-scores) - Add confidence indicators to help review extracted data * [Parsing Configuration](/docs/guides/parsers/parser-settings/parsing-configuration) - Full list of parser processing settings * [Credits and Billing](/docs/guides/troubleshooting/credits-and-billing) - Understand credit usage across parser options How is this guide? GoodBad [ Advanced table extraction Learn when to use advanced table extraction, how Auto/Enabled/Disabled work, and how to choose the right setting. ](/docs/guides/parsers/parser-settings/advanced-table-extraction)[ Confidence scores Understand how confidence scores work, what the numbers mean, and when to use them. ](/docs/guides/parsers/parser-settings/confidence-scores)