NurViewer · Table recognition
Tables across PDF pages
A long report splits one table across several pages and repeats its header. Manually joining each fragment in a spreadsheet can introduce duplicate headings or put rows in the wrong order.
THE PRACTICAL VALUE
Why this step deserves its own workflow
Compatible table fragments can be assembled across pages with repeated-header handling. Review continuity against the source rather than accepting page boundaries as the boundaries of your data. This helps when the useful unit is the full table, not one isolated page of a report.
A PRACTICAL SEQUENCE
Start with the material you actually need.
Check representative material before deciding how much more to process.
- Choose the pages containing the table and its continuation.
- Check that columns and headers really belong to the same table.
- Review the stitched result for missing rows and repeated headings.
EDITION & SCOPE
Know the scope before you commit.
Only compatible fragments can be joined. Changed columns, unrelated nearby tables or uncertain boundaries need review; this is not automatic perfect stitching for every report.
Free has no trial expiry: common-format reading, ordinary PDF annotations and supported ordinary document/image-to-PDF export remain available. Recognition, specialist formats and advanced tools have their own allowances or tier requirements.
Compare Free, Standard and Pro →Images may retain historical layouts. Demonstration books, dictionaries and media are not bundled.
A USEFUL QUESTION
Does joining pages prove the numbers are correct?
No. Continuity, structure and character accuracy are separate checks. Always verify critical values.
CONTINUE THE WORKFLOW
A useful next step.
Keep reading, understanding and organising around the same material.
Table recognition
Tables to editable Excel
A screenshot of a table is easy to send and hard to calculate with. Copying text often loses columns and empty cells, leaving you to rebuild the relationships before you can do any useful analysis.
Explore the workflow →Table recognition
Merged headers & empty cells
If a multi-level header is flattened or an empty cell disappears, the exported numbers can move under the wrong label. The result may look tidy while saying something different from the original.
Explore the workflow →Table recognition
Borderless table recognition
Many comparison sheets and reports use whitespace instead of grid lines. A generic extraction can turn aligned columns into prose, even though you need a table for sorting and comparison.
Explore the workflow →