Image to Excel: paste a table you can check

An image to Excel workflow is useful only if the values land in the right cells. A table can look right but lose leading zeroes. It may change decimal marks or shift a row too. Start with a clear image, extract the table and review the pasted cells before adding formulas. Try Excel's own picture feature or a clipboard route with tabs. This guide covers both. The small exercise uses sample figures. Follow the maths yourself. It is not a measured claim about OCR quality.
Choose the shortest route into cells
If you have the original workbook or an authorised CSV export, use that first. It preserves structure without recognising pixels. If the only source is an image, check whether your version of Excel offers Data from Picture. Microsoft's guide explains which versions have the feature. It also covers menu changes between systems. Do not assume that every Excel build has exactly the same feature or supported languages.
In a supported version, use Data, then From Picture, and choose the relevant file or clipboard option. Microsoft's official guide says, “Review the results”. That step is part of import, not an optional finishing touch. Correct highlighted issues and compare the surrounding cells before selecting Insert Data.
For a table visible in another app, a screen OCR tool can provide tab-separated rows for pasting. Lass0's plain-text table format uses tabs, as described in the format documentation. That is a clipboard workflow. It does not create a native .xlsx file. It cannot recover formulas hidden behind the values in a screenshot.
Prepare the image before extracting
Open the original image rather than a small chat thumbnail. Crop away unrelated paragraphs and controls while retaining the full header, all needed rows and units. A head-on, focused picture is easier to read than an angled phone photograph. If the grid is wide, make sure both ends remain legible; do not enlarge one side and accidentally omit the last column.
Keep a source copy beside the spreadsheet during review. Give it a descriptive filename or source reference. If the table is part of a PDF, note the page range and any caption. An amount may be read correctly but lose its currency or scale. That changes what the number means. Those labels belong in your working record even when they are outside the visible cell borders.
For a long PDF table, consider whole-document extraction instead of a chain of overlapping screenshots. Overlap creates duplicate rows; tight cropping can omit a boundary row. The PDF table guide explains how to count rows across page breaks. Apply the same completeness check before importing the result into Excel.
How do I paste tab-separated text into Excel?
Choose the cell where the top-left corner should go. Set ID columns to text before pasting. This helps keep leading zeroes where they are part of the code. Paste the extracted table and confirm that tabs became column boundaries and newlines became rows. Did everything land in one cell or column? Check the copied text and import options. Do not try to fix the grid with spaces.
Use a blank sheet for the first paste. That prevents accidental overwriting and makes the imported range easy to count. Compare the number of data rows and columns with the source. Then inspect the first row, a middle row and the final row, followed by every field whose error would matter. For a small table with important values, check every cell. A spot check is not enough.
If a column has mixed dates, codes and numbers, decide its intended type before accepting automatic conversion. A string such as 03/04 can mean different dates under different locales, or it may not be a date at all. Keep the original text until the meaning is established. Formatting is not a substitute for understanding the field.
A checking exercise with a useful trap
The following figures are illustrative. They demonstrate a review method and do not represent a live customer sheet or an OCR benchmark. Keep the item codes as text. The first zero is part of each code.
Table: illustrative order lines. The expected amount is quantity multiplied by unit cost; the checked total is £42.50.
| Code | Quantity | Unit cost (£) | Expected amount (£) |
|---|---|---|---|
| 0012 | 3 | 5.00 | 15.00 |
| 0007 | 2 | 8.50 | 17.00 |
| 0041 | 1 | 10.50 | 10.50 |
| Total | 6 | Not applicable | 42.50 |
Check the codes first. A paste that changes 0012 into 12 has lost information even though the number is mathematically equivalent. Next check quantities and costs. Recalculate each amount in a separate column using verified inputs. Compare the total, then review row associations. Two wrong cells can cancel each other out. A matching total helps, but does not prove every cell is right.
Now imagine that 8.50 was read as 850. A currency format may display £850.00 neatly. The polished appearance makes the error easier to overlook. Compare the character positions in the image, especially decimal marks and negative signs, before applying final styles. Keep a note of corrections when the sheet will be reviewed by someone else.
Why does screenshot table to Excel paste go wrong?
Recognition and import are separate stages. OCR can misread a character or group the wrong columns. Excel can then interpret a correctly extracted string as a date, number or formula. Diagnose the stage by pasting the same output into a plain-text editor. If the tabs and values are wrong there, return to extraction. If they are right there but wrong in Excel, review import and cell types.
Multi-line cells are another trap. A wrapped product description can be mistaken for a second row. Merged headings can shift the apparent column count. A note beneath the table may be imported as data. Select a simpler rectangular region or restructure the output against the source, keeping a record of the change. Do not silently invent missing cells to make the grid line up.
The Tesseract quality guidance discusses source issues such as skew and noise. Those principles help explain why a clearer capture can improve recognition, but they are not an accuracy guarantee for every engine. If a value is genuinely unreadable, ask for a better source rather than choosing the number that makes a total balance.
Can I recover formulas from a table image?
Usually the image shows displayed values, not the workbook's underlying formulas, cell types, validation rules or hidden sheets. OCR can extract the visible characters. It cannot establish how the original author calculated them. If you need formulas or audit history, obtain the workbook or an authorised data export from its owner.
You can create your own formulas after checking the input, but label them as your calculations. Keep source values separate from derived results. That makes it easier to spot whether a discrepancy came from recognition, typing, locale conversion or your formula. It also prevents a reviewer from assuming that your workbook is an exact reconstruction of the original.
Finish the import before using the numbers
Record the source, check all required rows and preserve units. Review identifier columns, decimals, signs and missing-value conventions. Only then sort, filter or calculate. Sorting can hide a shifted row. It moves values away from the order in which you first checked them.
Try a small non-sensitive table through the screenshot extraction workflow, then use the OCR review checklist to assess the result. If you need this every day, compare the time spent correcting representative tables rather than the speed of the first paste. The useful saving is a verified spreadsheet, not simply fewer keystrokes at the start.
Questions, answered
Does Lass0 export a native Excel workbook?
This route pastes table text with tabs into cells. It does not create an .xlsx file. It cannot recover the formulas behind displayed values.
How do I stop Excel removing leading zeroes?
Set code or ID columns to text before you paste. Then compare the strings with the source. A number format alone may not keep the original value.
Can I convert a PDF table to Excel the same way?
Yes, once you have read and checked the table. Check page breaks, repeated headers and units. Review cell types before using the data.
Put it into practice.
Explore the related Lass0 workflow or download the app to try it with a non-sensitive example.