NurViewer · 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.

THE PRACTICAL VALUE

Why this step deserves its own workflow

NurViewer considers aligned content as well as visible rules. When a layout is ambiguous, review the candidate and explicitly keep it as a table if that matches your purpose. This gives you control over the interpretation instead of silently exporting every list as a spreadsheet.

A borderless comparison retained as a table after explicit review.
A borderless comparison retained as a table after explicit review. View full screenshot ↗

A PRACTICAL SEQUENCE

Start with the material you actually need.

Check representative material before deciding how much more to process.

  1. Recognise a page containing aligned, borderless content.
  2. Check the candidate columns against the original.
  3. Keep it as a table when appropriate, then export and review.

EDITION & SCOPE

Know the scope before you commit.

Manual confirmation chooses the interpretation; it cannot repair incorrect column boundaries or OCR text. Skew, dense layouts and weak alignment can still cause missed or extra tables.

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

Will every list be forced into a table?

No. Ambiguous candidates can require your review, so a contents page or prose list is not silently assumed to be a valid table.

NurViewer · Windows

Make room for the work you wanted to do.

Explore the Windows workflows, compare the current plans and check verified release availability.