Start with honest expectations
Urdu OCR (اردو او سی آر) is harder than English OCR. Connected letterforms, stacked Nastaliq calligraphy, and missing or dense diacritics all raise the error rate. Photo2Text is best-effort: a sharp scan of plain print can look great; a dim, tilted phone photo of ornate type will not. Improving the image usually beats switching tools. When your photo looks ready, open the Urdu converter and run a quick Extract pass.
Lighting and contrast
- Use diffuse daylight or a lamp that does not create a hotspot glare.
- Dark ink on light paper outperforms faded photocopies.
- Avoid patterned tablecloths and busy posters behind the page.
Cropping and framing
Fill the frame with the paragraph you need. Margins, stamps, seals, and neighboring columns add noise. If a page has multiple columns, crop one column at a time. Keep the phone parallel to the page so lines stay roughly horizontal.
Resolution without excess
Text should look crisp when viewed at 100% on your screen. That is a better rule of thumb than chasing a specific DPI number. Extremely large photos mostly cost time; our tool downscales widths above 2000px before OCR runs.
Language selection
On the Urdu page, choose Urdu (or English + Urdu for mixed pages), then Extract. After the first model download, switching images with the same language reuses the worker for the session.
Nastaliq vs Naskh: why the font matters
Urdu is printed in two main styles, and the style decides how hard the OCR job is. Naskh is upright and even: letters sit on a clear baseline, words are spaced regularly, and each character keeps a familiar shape. Most textbooks, official forms, and simple documents use Naskh or a Naskh-like font, and these are the pages that OCR handles best. Nastaliq is the slanted, flowing calligraphic style used by most Urdu newspapers and many books: letters stack diagonally, words slope downward from right to left, and characters join in dense ligatures that change shape depending on their neighbours. That beauty is exactly what makes Nastaliq hard for an OCR engine, because the same letter can look very different in different words, and the diagonal layout breaks the engine's assumption that text runs in straight horizontal lines. Decorative headline fonts and hand-drawn calligraphy are harder still, and should be treated as pictures to retype rather than text to extract. When you have a choice between two copies of the same content, pick the Naskh version, or the copy with the larger, plainer print, and save the Nastaliq original for reading by eye.
Urdu document types and what to expect
Different Urdu documents behave differently, and knowing what to expect stops you blaming the tool for a hard original. Printed books and textbooks in plain Naskh are the best case: even lines, clean paper, and consistent type usually give a usable draft with only light proofreading. Newspapers are harder because Nastaliq columns are narrow, the print is small, and photos and headlines interrupt the flow, so crop one column at a time and expect more errors in headlines than in body text. Official letters and certificates often mix printed Urdu with handwritten names, stamps, and signatures, and the printed parts extract well while the handwritten parts usually do not, so plan to type names and numbers yourself. Old or photocopied pages suffer from faded ink, yellowed paper, and bleed-through from the other side, and a gentle contrast boost or a re-scan in good light helps more than running the same dull image twice. Images forwarded on chat apps are the weakest source of all, because the app compresses them, and a forward of a forward can turn crisp print into mush, so always ask for the original file when the text matters.
Step-by-step Urdu OCR workflow
- Pick the clearest copy. A flat scan beats a tilted phone photo, and an original file beats a chat forward. If the page is creased, flatten it first.
- Crop one block at a time. Choose a single paragraph or a single newspaper column, and leave a small margin so no line is cut at the edge.
- Choose Urdu on the converter. Open the Urdu OCR page, select Urdu, and use English + Urdu only when the page genuinely mixes both scripts.
- Extract and skim. Run Extract, then read the first few lines against the image. If they are mostly right, continue; if they are gibberish, stop and fix the image first.
- Re-crop the hard lines. Headlines, footnotes, and lines near a fold often need their own tighter crop with better light.
- Proofread before you reuse the text. Check names, numbers, and dates character by character, because those are the words a spellchecker cannot catch.
Handling mixed Urdu and English pages
Urdu documents often carry English alongside them: an English heading over an Urdu body, a form with English labels and Urdu answers, or an address written in Latin letters at the bottom of a letter. The safest approach is to decide which script carries the information you need and crop for it first. When both scripts matter in the same block, use the combined English + Urdu mode, and expect the English words to come out cleaner than the Urdu ones, because Latin letters are simpler shapes. Roman Urdu, where Urdu words are written in Latin letters, is a special case: run it with English selected, not Urdu, because the characters on the page are Latin even though the language is Urdu. Numbers need attention too: a page can mix Latin digits with Urdu or Arabic-Indic digits, and the wrong language choice can turn one set into the other, so check every number in your proofreading pass. When a bilingual line comes out jumbled, split it into two crops, one per script, and join the results yourself.
Diacritics, dots, and common letter confusions
Urdu letters are distinguished by dots more than by shape, and dots are the first thing a blurry photo loses. The letters for b, t, and th share one basic shape and differ only in the number and position of dots, and the same is true of other letter groups that differ only by dots above or below the line. When a dot fades or merges with the letter, the engine guesses, and the guess changes the word entirely, so a proofreading pass that checks dots is not optional. Diacritics, the small marks for short vowels such as zabar, zer, and pesh, are a second problem: most printed Urdu leaves them out, and when they do appear, they are tiny and easily dropped by OCR. That usually does not matter, because a fluent reader supplies the vowels from context, but it matters for poetry, religious text, and children's learning material, where the marks carry meaning. Also watch for letters that join into a single flowing shape in Nastaliq: two short words can merge into one, or one long word can split into two, and the only fix is to compare the output with the image word by word. If a word looks wrong and you cannot tell why, zoom into that exact spot in the image and read the dots before you trust the text.
Proofreading Urdu OCR output
Proofreading Urdu output takes a different eye than proofreading English, because the errors hide in small details. Read the result aloud in Urdu: a sentence that sounds wrong usually has a dot error or a joined word, and your ear will catch it faster than your eye. Check proper names first, because a misread name is the hardest error to spot later, and then check numbers, dates, and amounts digit by digit. Compare the text with the image line by line rather than reading the output on its own, because on its own a wrong word can look plausible. Watch for spacing errors in particular: Nastaliq output often drops the space between two words or adds one inside a word, and both mistakes change the meaning. Keep the image open beside the text until you are done, and do not delete it afterwards when the document matters, because the image is the only way to settle a doubt later. A ten-minute check on a one-page letter is normal, and it is still far faster than typing the whole page by hand.
When to reshoot instead of re-running OCR
Running the same image through OCR twice gives the same result twice, so when the output is poor, change the image, not the tool. Reshoot when the photo is blurry, when glare washes out a corner, when the page leans so far that lines slope, or when the text is too small in the frame. Move closer, add soft light from the side, flatten the page, and take the shot again with the phone parallel to the paper. A scan is worth the effort for anything longer than a page, because a flatbed scan removes tilt, shadow, and focus problems in one step. The only time a second run on the same file helps is when you change the settings, such as switching from Urdu alone to English + Urdu for a mixed page, or cropping tighter around a single paragraph that was lost in a full-page run. If three different crops of the same page all fail in the same place, the problem is the print itself, and that line is a job for typing, not for OCR.
Related reading
Ready to extract? Try Urdu OCR on a clear photo. Need العربية as well? Open Arabic OCR. Beginners can also follow how to pull text from any image. Also useful: screenshot OCR, JPG camera OCR, PNG to text, the homepage converter, and our OCR comparison guide. Also: About, Contact, and the sitemap.
Sources & further reading
- Tesseract language data & training notes, how open-source OCR models are prepared
- Arabic script overview (Unicode), connected Arabic-script letterforms that also affect Urdu
- Tesseract.js project, browser OCR used on Photo2Text
Try our OCR tools
Same private browser OCR. Pick the page that matches your language or file type.
- Image to Text (Home)Free private OCR for English, Urdu, and Arabic images.
- Urdu OCRExtract Urdu text from photos in your browser.
- Arabic OCRConvert Arabic images to editable text privately.
- Screenshot to TextPull text from error messages, chats, and receipts.
- JPG to TextOCR for JPEG camera photos and scans.
- PNG to TextOCR for sharp PNG screenshots and scans.