Frequently asked questions

15 questions about Image Table to Excel OCR · Last updated 2026-11-06

Author Jikwang Kim (Operator)Last updated bal.pe.kr 마이크로 SaaS
Q1. Are images really not uploaded?
Yes. The site is static hosting (S3 + CloudFront) — there is no upload endpoint to send anything to. Open DevTools → Network and run OCR: no request carries your image. The only external requests are the first-run OCR engine/language downloads from cdn.jsdelivr.net and analytics. Language data is cached in IndexedDB, but the engine files rely on the normal HTTP cache, so offline use is not guaranteed.
Q2. Which image formats are supported?
PNG · JPG · WEBP are the officially supported formats. Most browser-readable formats (GIF, BMP) also work, but we only test the three. PDF is not supported yet — export the PDF page to PNG and upload that.
Q3. How accurate is Korean recognition?
It varies too much with image quality to give one number, and we have not published our own accuracy measurements. The Tesseract docs say results are best with sharp images of 300 dpi or more, level text lines and some border around the text, and that tables are a known weak spot. Clean print and screenshots read fairly well; handwriting and blurry scans drop sharply — always review the output.
Q4. Why not use CLOVA OCR or Google Vision?
Those APIs generally recognise more accurately, but (1) need a cloud account and API key with possible usage-based charges and (2) send your image to their servers. This tool prioritises free, in-browser use, so it runs tesseract.js.
Q5. How big an image can I upload?
Practically keep images under ~5MB and ~3000px on the long edge. Beyond that, the browser tab may get memory-pressed. Cropping to just the table region is faster and more accurate anyway.
Q6. Why is the first run slow?
The OCR engine and language data — about 8.6MB (Korean 1.6MB, English 3.0MB, engine 4.1MB, compressed) — are downloaded from the jsDelivr CDN. Language data is cached in IndexedDB and the engine is usually served from the browser cache, so later runs start faster.
Q7. Rows / columns split incorrectly — how do I fix it?
Double-click any cell in the preview to edit inline. To drop a whole row, tick its checkbox and "Delete selected rows". Missing rows can be added with "Add row". For heavy column restructuring, export to XLSX first and edit in Excel.
Q8. Korean "원" or "%" symbols keep garbling.
We post-correct patterns like 12,345 원 into 12,345원. But if tesseract already mis-read the glyph, clean-up can't recover it — raise the resolution or fix the cell manually.
Q9. How are merged cells handled?
We only see pixels, not merge metadata. Text spanning a merged range typically lands in the leftmost column of that range. Split or move cells in the preview as needed, or re-merge in Excel after exporting.
Q10. Can I paste the result into Google Sheets?
Yes. The "Copy to clipboard" button above the result copies the table as tab-separated text (TSV), so pasting into Google Sheets or Excel fills separate cells. For a file, download XLSX and use File → Import. CSV export includes a UTF-8 BOM so Korean renders in Excel.
Q11. Can you batch-convert multi-page PDFs?
Single images only for now; multi-page PDF batch OCR is on the roadmap. Export each PDF page to PNG (e.g. Preview.app on macOS, or any PDF viewer) and process them one by one. Uploading a new image replaces the previous result, so download or copy each page first.
Q12. Does it work on mobile?
Works in current mobile browsers that support WebAssembly and Web Workers (iOS Safari, Android Chrome, etc.). Mobile memory/CPU limits favour smaller table images; use a desktop for large ones.
Q13. Do you log or store anything?
We use GA4 and Naver Analytics for visit counts and usage stats that carry no content (file size/type, number of recognised rows/columns). No image contents or recognised text leave your browser — nothing is transmitted to begin with. The tool’s code does not use localStorage; IndexedDB only caches the tesseract language data.
Q14. My company blocks file uploads. Is this tool safe to use?
The site is pure static hosting (S3 + CloudFront) — there is no backend to receive anything. Parsing and OCR happen inside your browser in the tesseract.js WebAssembly runtime. Some enterprises restrict even third-party JS, so check with your security team. On-prem builds are available on request.
Q15. Does handwritten text work?
The official Tesseract FAQ says you can try, but it won't work very well because Tesseract is designed for printed text. Handwritten tables need a dedicated handwriting OCR service.