PDF TABLE EXTRACTION WORKFLOW
Extract the table, preserve the review trail
The hard part is not copying visible text. It is proving which pages, rows and coordinates were supported, preventing spreadsheet payloads and refusing to call an uncertain result complete.
Decision 1: is this a supported digital-text PDF?
Open the source in an independent viewer and try selecting a short cell value. Selection alone is not proof, but it helps distinguish digital text from an image-only scan. Use the extractor only when the file is authorized, begins with a normal PDF signature, is no larger than 8 MiB and exposes no more than 50 page objects.
- Encrypted: stop. The tool returns BLOCK and does not attempt decryption.
- Scanned or image-only: stop the extraction claim. The tool returns INDETERMINATE because it performs no OCR.
- Rotated, skewed, unresolved-font or unsupported stream: retain the coverage warning and use manual review or another bounded workflow.
- Digital text with stable coordinate rows: continue, but still compare the result with the page.
Decision 2: limit the job before tuning columns
- Record the exact source file and keep it unchanged during review.
- Enter only the pages that contain the target table, for example
3-5. A page selection is part of the extraction policy and changes the receipt hash. - Run automatic anchors first. Inspect the coordinate map rather than judging the spreadsheet alone.
- If columns are grouped incorrectly, enter vertical separators in PDF points such as
200,400. A separator divides the page into bands; it does not make unsupported text safe. - Select only the detected table IDs needed for the handoff. Rebuild the evidence packet after changing the selection.
Do not move separators until the output “looks right” and then forget the policy. The exact page, table and boundary choices are evidence and belong in the receipt.
Decision 3: read PASS, BLOCK and INDETERMINATE literally
PASS
The selected subset has a stable table and no known unsupported signal. PASS is bounded; it does not certify totals, dates, identities, currencies or the unseen remainder of the PDF.
BLOCK
The PDF declares encryption. No text extraction is attempted. Create an authorized decrypted copy outside FastTool and treat it as a new input with a new hash.
INDETERMINATE
A stable result cannot be claimed. The reason may be scanned content, incomplete decoding, rotation, text crossing a manual separator, a sparse/merged-like row or no stable table.
Input error
A malformed signature, excessive size or invalid page/boundary expression unlocks no export. Correct the input; never reuse a stale packet.
Decision 4: choose the artifact for the handoff
- CSV: long-form cell ledger with table, page, row and column identifiers. Formula-leading values are apostrophe-neutralized.
- XLSX: the same ledger as inline strings, with formula-leading values also neutralized. It is designed for review, not for preserving visual PDF layout.
- JSON: raw extracted values, selected policy, coordinates, coverage reasons and limits. Treat it as potentially sensitive.
- SVG: approximate supported text boxes and column guides. It is not a rendered PDF page.
- Markdown: compact QA handoff with verdict, hashes, warnings and review instruction.
- Receipt: exact input, policy and artifact hashes. Hash parity proves byte identity, not semantic correctness.
Required review before import
- Verify the receipt core and every artifact with Receipt Verifier.
- Compare column headings and every exported row with the original PDF in an independent viewer.
- Check totals, signs, decimal separators, dates, currency labels and blank cells separately.
- Confirm the number of selected pages and tables matches the intended scope.
- Keep the original PDF, extraction policy, artifacts and receipt together. If the source or policy changes, discard the old approval.
For financial, legal, medical, regulatory or safety decisions, this browser tool is only an extraction aid. A qualified reviewer remains responsible for the source interpretation.
Common failure patterns
- Copy and paste into Excel: loses source coordinates, can collapse columns and may activate formula-leading content.
- “The PDF looks normal”: visual appearance does not prove the underlying text operators are supported or complete.
- Run OCR and accept it: OCR introduces its own recognition errors and needs a separate confidence and visual verification workflow.
- Trust a green badge: PASS covers only the selected bounded subset and must remain attached to its exact receipt.
- Send only XLSX: the recipient cannot independently check scope or bytes without the JSON, map, original and receipt.
Sources, correction and review date
Method reviewed 4 August 2026. Primary references: PDF / ISO 32000 resources, RFC 4180, OWASP CSV Injection, and ECMA-376.
Report a stale source, unsafe export, fixture mismatch or unsupported claim to [email protected]. Include the exact statement, fixture or input class, and reproduction steps; never email confidential source data.