Features & Usage Limits

DocsToSheets usage and features are governed by your subscription plan.

Subscription Plans

You can manage your subscription directly from the Billing page of your DocsToSheets Dashboard.

Feature	Free Plan	Pro Plan	Enterprise Plan
Documents / Month	50	1,000	Custom / Unlimited
Max File Size	10 MB	50 MB	50 MB
Connected Sheets	1	Unlimited	Unlimited
Custom Mailboxes	1	5	Unlimited
API / MCP Access	No	Yes	Yes
Priority Queueing	Standard	High Priority	Dedicated Queue

Ingestion Limits & File Constraints

Whether you are uploading files via the Web dashboard, emailing them to a custom mailbox, or calling the REST API/MCP tools, the following constraints apply:

File Sizes

Maximum File Size (Dashboard Uploads):
- Free Plan: 10MB per file
- Pro/Enterprise: 50MB per file
Maximum Email Ingest Size: 50MB total email payload (including headers and all attachments).

Supported Formats

DocsToSheets processes raw document files directly using AI models optimized for document layout analysis:

Documents: PDF (.pdf)
Images: JPEG (.jpg / .jpeg), PNG (.png), WebP (.webp), TIFF (.tiff)

Note: Microsoft Word (.docx) and other text formats are not supported directly; please convert them to PDF before uploading.

Email Mailbox Limits

Maximum Attachments: A single incoming email will process a maximum of 10 attachments. If an email contains more than 10 attachments, only the first 10 will be parsed, and the remaining files will be ignored.
Wildcard Domain Senders: You can authorize entire domains (e.g. *@mycompany.com) to submit documents to a mailbox, subject to your account’s monthly document limits.

Field Validation

For the full walkthrough of field configuration, see Fields, Columns & Sections.

Each mailbox field can have at most one validation rule. Supported rules are:

Email: checks that a non-empty value looks like an email address.
US ZIP: checks 12345 and 12345-6789 formats.
Regex: checks a full-value pattern for stable IDs or codes.
Formula: checks an arithmetic comparison — usually same-row (such as a line total equaling quantity × unit price), but a document-level field can also check a printed total against the sum of a line-item column, and a line-item field can check against a document-level value.

Validation marks extracted, manual, or edited values as invalid for review. It does not invent replacement values, and empty optional fields remain valid.

Computed Fields (Formulas)

See Fields, Columns & Sections for the complete formula reference and examples.

Any numeric column can be a computed field instead of an extracted one: you write a formula and DocsToSheets calculates the value, so it is always consistent with the fields it depends on (and is never asked of the AI).

Formulas support numbers, the operators + - * /, parentheses, and round(value, decimals). They can reference other fields in the same place — a document-level field sees the other document-level fields; a line-item field sees the other columns in its row. Two shortcuts reach across that boundary:

Totaling a line-item column — a document-level field can roll up a repeating table with sum, count, avg, min, or max. Example: sum(line_items.line_total) for an invoice grand total.
Reading a document-level value from a line — a line-item field can use header.<field>. Example: base_amount * header.tax_rate.

When a table has no rows, sum and count are 0; avg, min, and max are left blank.

Blank cells count as zero. In a computed field, an empty value is treated as 0 — so a weekly total like mon + … + sun still adds up even when some days are left blank, just like a spreadsheet. (A value that is present but not a number, such as "n/a", leaves the result blank so the bad value is noticeable.) Formula validation rules work the other way: if a field they reference is blank, the rule is reported as “could not be checked” rather than failing the row — so an incomplete entry isn’t marked invalid just for having an empty field.