A payslip carries your name, your salary and your tax number; a timesheet carries where you were every day. Drop either as a PDF or a photo and it comes back as cells you can edit — read inside this tab, on your own machine, with nothing sent anywhere.
They are already read in this tab. A pass unlocks every row of every file you convert over the next 7 days, in this browser — and on any other once you sign in.
Numbers, percentages and amounts are written as numbers, so they add up in the spreadsheet.
Every document on this site is read in the tab, but a payslip is the one where it stops being a technical detail. On one page sit your full name, your home address, your payroll number, your tax code, what you earn and what you are left with — and in some countries a national insurance or social security number beside it. That is the document people hesitate over before uploading to a free converter, and they are right to.
There is nothing here to upload to. The reading happens in code running in this tab: no endpoint receives the file, nothing is stored, and closing the tab is the whole of the deletion. You can watch the network panel of your developer tools while you convert, which is the only version of this promise that is worth anything.
If your payslip arrived as a PDF from a payroll system, the figures are already text inside the file. Those are taken exactly as written — 2,480.00 stays 2,480.00, because nothing recognises anything. The page says so under the result: read from the PDF's own text, with no confidence percentage, because there is no uncertainty to report.
A photograph, a scan, or a PDF that is really a scan has to go through OCR, and OCR can misread. Then a confidence figure does appear, every cell stays editable, and the honest instruction is the same one we give for scanned statements: compare the figures that matter against the paper before you rely on them.
It does not check the arithmetic, and that is worth stating plainly because our bank statement reader does. A statement carries a running balance, so every row can be proved against the one above it. A payslip carries no such chain: gross, deductions and net are three numbers printed by the same system, and adding them up again proves only that the page read them consistently — not that the payroll was right. Where a document gives us something to check against, we check and say so. Where it does not, we say that instead of inventing a tick.
It also does not interpret. A tax code is copied, not explained; a deduction is a row, not advice. If a figure looks wrong, the person to ask is your employer's payroll team, and the spreadsheet this page gives you is a decent way to show them what you are looking at.
Columns are found by the gaps between them, so the usual payslip layout — payments on the left, deductions on the right — occasionally comes back as one wide table where a row pairs an earning with an unrelated deduction. The cells are all correct; the pairing is not. When that happens, crop the picture to one block and convert it twice, or widen the gap by exporting the PDF at a larger size.
A multi-page document is read one page at a time, starting with the first. For a monthly timesheet that runs over two pages, convert each page and stack the two sheets — which is also how you keep the week numbers from running together.
Something else? Write to support@ocrsnip.com.
No. There is no upload step and no server on this site that could receive a file — the page reads the document with code running in your own browser. Open the network panel of your developer tools and convert the sample: nothing carrying the document leaves your machine. Nothing is stored either, so there is nothing to delete afterwards.
Much better, if it came from a payroll system rather than a scanner. Then the numbers are text inside the file and are taken exactly as written, with no recognition involved. A photo or a scan goes through OCR, which is good but not perfect — that is why every cell stays editable and why a confidence figure is shown for those and not for the other.
No, and it does not pretend to. The page reads what is printed; it has nothing to check the figures against, because a payslip carries no running balance the way a bank statement does. What it gives you is the numbers in a spreadsheet, which is the form in which a disagreement with payroll is easiest to have.
That is the two-block layout: columns are found by the white space between them, and on a narrow payslip the gap down the middle can be too small to count as a gutter. Crop to one block and convert it twice, or export the PDF larger. The cells themselves are read correctly either way — it is the pairing across the middle that is wrong.
One document at a time on this page. For a year of them the quicker route is usually the bank side: the net pay lands in your account every month, and bank statement to Excel turns twelve months of that into one sheet in a single pass.
ocrsnip