A 30-page scanned contract. A super-tall screenshot of a long article. A folder of 200 photos from a research trip. Single-page OCR doesn't cut it.
This guide covers how to extract text from long images and large batches of images efficiently — what works for one-off jobs, what works at scale, and what to avoid.
Two Different Problems
People often lump these together, but they need different solutions:
- Long-image OCR: one very tall image (a full-page screenshot, a scrolling capture, a panoramic photo)
- Batch OCR: many separate images you want to process together (a folder of scanned pages, photos from a meeting whiteboard sequence)
Long-Image OCR
Method 1: Single-Pass AI OCR (Recommended)
Modern AI OCR models process the entire image in one shot, no matter how tall — up to the platform's resolution limit (~32 MP for most).
With :
- Upload your long screenshot or scroll capture directly
- The AI reads the whole image — order is preserved top to bottom
- Get one continuous text output
When this works: screenshots, scroll captures, long-article photos, document scans up to ~32 megapixels.
Method 2: Split + Merge (For Extra-Tall Images)
If your image exceeds the resolution limit (rare — would be 10000+ pixels tall):
- Split the image vertically into 2–3 chunks
- Leave a ~50 px overlap between chunks (so no line is cut in half)
- OCR each chunk separately
- Concatenate the text outputs, deduplicating overlap lines
This is the only manual fallback you'll need.
Batch OCR
Method 1: One-by-One (Small Batches, Free Tier)
For 5–10 images, just upload them one at a time. With img2txt.app's free tier (3/day anonymous, 6/day registered), this works without cost.
Method 2: Pro Plan for Sequential Processing
For 50–500 images:
- Upgrade to img2txt.app Pro ($4.9/month, unlimited usage)
- Upload images in batches throughout the day
- Each conversion takes ~5 seconds
For a 200-image batch: ~17 minutes of wall-clock time.
Method 3: API + Script (Power Users)
If you have hundreds or thousands of images, write a script that:
- Reads each file in a directory
- POSTs to the OCR API
- Saves the text output with the original filename
img2txt.app exposes an OCR API for Pro subscribers — combine with a simple Node.js or Python loop and the entire workflow takes 30 lines of code.
Method 4: Existing Pipelines (Tesseract Batch)
If you'd rather self-host:
for f in *.jpg; do
tesseract "$f" "${f%.jpg}" -l eng
doneStrengths: Free, offline, scales infinitely. Weaknesses: Tesseract is markedly worse than AI OCR on real-world images. Acceptable for clean scans only.
Picking the Right Approach
| Volume | Image Type | Recommended |
|---|---|---|
| 1–6 / day | Anything | img2txt.app free tier |
| 50–500 | Anything | img2txt.app Pro |
| 1000+ / month | Anything | img2txt.app API + script |
| 1000+ / month | Clean scanned printed pages | Self-hosted Tesseract |
| Very tall single image | Anything | AI OCR in one pass |
| 30+ MP single image | Anything | Split & merge manually |
Tips for Batch & Long-Image OCR
- Name files in order before uploading. Use
page-01.jpg,page-02.jpg… notIMG_3849.jpg - Resize ultra-high-resolution photos. A 50 MP photo isn't more OCR-friendly than a 12 MP one — and uploads slower
- Strip metadata if uploading sensitive material. EXIF can carry GPS, device info
- Spot-check the first and last item. OCR quality is consistent within a batch, so the first item's accuracy predicts the rest
- For long scrolling screenshots, use a vertical scroll tool like the iOS scroll capture or Chrome's "Capture full size screenshot" devtool command — it produces higher-quality long images than manually stitching
- Avoid stitching from multiple separate screenshots — alignment errors at the seam confuse OCR. Single scroll captures are cleaner.
Common Pitfalls
- Photos taken at an angle: correct perspective in Photoshop / on-device editor before OCR
- Inconsistent lighting across the batch: OCR each in the lighting it was captured in, don't batch-correct
- Mixing portrait + landscape orientations: the model handles both, but rotate to a consistent orientation if accuracy matters
Summary
For most users, batch and long-image OCR aren't actually hard in 2026:
- One image at a time, including very long screenshots → free with
- A folder of dozens of images → Pro plan unlocks unlimited
- Thousands of images → API + script
If you also need to translate the batch (e.g., a stack of foreign-language documents), handles OCR + translation in one upload.
FAQ
Can OCR handle very long screenshots?
Yes. AI OCR tools like process long screenshots in one go — the model reads the entire image, not just a fixed window. There's no need to split the image manually for most cases.
How do I extract text from a batch of photos at once?
For a few photos, upload them one by one (free tier). For large batches (50+), use a Pro plan with unlimited usage, or scriptize via API. img2txt.app's roadmap includes a batch upload feature.
What if my image is too tall and gets compressed?
Most tools accept tall images up to ~32 megapixels. For taller images (full-page article screenshots, infinite-scroll captures), split into 2–3 vertical slices with ~50px overlap between them, OCR each, then concatenate.
Will batch OCR preserve the order of pages?
If you upload files in a sortable naming convention (page-01.jpg, page-02.jpg…), yes. Most tools process and output in filename order, so name files carefully before uploading.
Is batch OCR free?
Most free tiers limit batch size. gives 3 free conversions/day anonymously, 6 registered. For 50+ images at once, Pro plans ($4.9/mo) offer unlimited usage.

