The tesseract package provides R bindings Tesseract: a powerful optical character recognition (OCR) engine that supports over 100 languages. The engine is highly configurable in order to tune the detection algorithms and obtain the best possible results.

Keep in mind that OCR (pattern recognition in general) is a very difficult problem for computers. Results will rarely be perfect and the accuracy rapidly decreases with the quality of the input image. But if you can get your input images to reasonable quality, Tesseract can often help to extract most of the text from the image.

Extract Text from Images

OCR is the process of finding and recognizing text inside images, for example from a screenshot, scanned paper. The image below has some example text:


eng <- tesseract("eng")
text <- tesseract::ocr("", engine = eng)
This is a lot of 12 point text to test the
cor code and see if it works on all types
of file format.

The quick brown dog jumped over the
lazy fox. The quick brown dog jumped
over the lazy fox. The quick brown dog
jumped over the lazy fox. The quick
brown dog jumped over the lazy fox.

Not bad! The ocr_data() function returns all words in the image along with a bounding box and confidence rate.

results <- tesseract::ocr_data("", engine = eng)
print(results, n = 20)
# A tibble: 60 x 3
   word  confidence bbox           
   <chr>      <dbl> <chr>          
 1 This        89.9 36,92,96,116   
 2 is          89.9 109,92,129,116 
 3 a           92.4 141,98,156,116 
 4 lot         93.3 169,92,201,116 
 5 of          91.4 212,92,240,116 
 6 12          91.6 251,92,282,116 
 7 point       93.0 296,92,364,122 
 8 text        89.5 374,93,427,116 
 9 to          93.6 437,93,463,116 
10 test        90.6 474,93,526,116 
11 the         87.1 536,92,580,116 
12 cor         82.7 36,132,81,150  
13 code        91.1 91,126,160,150 
14 and         91.8 172,126,223,150
15 see         88.1 236,132,286,150
16 if          96.4 299,126,314,150
17 it          88.3 325,126,339,150
18 works       90.4 348,126,433,150
19 on          95.0 445,132,478,150
20 all         91.6 500,126,529,150
# ... with 40 more rows

Language Data

The tesseract OCR engine uses language-specific training data in the recognize words. The OCR algorithms bias towards words and sentences that frequently appear together in a given language, just like the human brain does. Therefore the most accurate results will be obtained when using training data in the correct language.

Use tesseract_info() to list the languages that you currently have installed.

[1] "/Users/jeroen/Library/Application Support/tesseract/tessdata/"

[1] "spa" "eng" "nld" "kor" "kat" "osd" "fra" "jpn"

[1] "3.05.01"

 [1] "ambigs.train"     "api_config"       "bigram"           "box.train"        "box.train.stderr"
 [6] "digits"           "hocr"             "inter"            "kannada"          "linebox"         
[11] "logfile"          "makebox"          "pdf"              "quiet"            "rebox"           
[16] "strokewidth"      "tsv"              "txt"              "unlv"            

By default the R package only includes English training data. Windows and Mac users can install additional training data using tesseract_download(). Let’s OCR a screenshot from Wikipedia in Dutch (Nederlands)

(dutch <- tesseract("nld"))
<tesseract engine>
 loaded: nld 
 datapath: /Users/jeroen/Library/Application Support/tesseract/tessdata/ 
 available: spa eng nld kor kat osd fra jpn 
text <- ocr("", engine = dutch)
Geschiedenis van de stad Utrecht

In de geschiedenis van de stad Utrecht vond reeds in de prehistorie
kleinschalige bewoning plaats. De Romeinen bouwden rond 50 n.Chr. in het
kader van een zeer omvangrijk militair bouwproject langs de toenmalige
Rijnloop in Utrecht het fort Traiectum ter hoogte van het Domplein. Hierdoor
werd de grondslag voor de stad gelegd. Na het venrek van de Romeinen
rond 270, vestigden in het midden van de 5e eeuw Franken zich in de regio.
Vanaf de 7e eeuw tot het begin van de 8e eeuw zou dat tot conflicten met
Friezen leiden.

Rond het jaar 700 arriveerden Angelsaksische missionarissen om het
gebied te kerstenen en vestigden in het oude Romeinse for1 daarvoor hun
basis onder Frankische bescherming. Het groeide uit tot de burcht Tracht en
het kerkelijk centrum. Hiernaast ontstond in de 10e eeuw met Stathe een
bloeiend handelscentrum met koop- en ambachtslieden.

In 1122 verkreeg Utrecht stadsrechten en kon daarop werden stadswallen
met een verdedigingsgracht om de stad aangelegd. Door verdere groei was
Utrecht tot halverwege de 16e eeuw de grootste stad van de Noordelijke

As you can see immediately: almost perfect! (OK just take my word).

Preprocessing with Magick

The accuracy of the OCR process depends on the quality of the input image. You can often improve results by properly scaling the image, removing noise and artifacts or cropping the area where the text exists. See tesseract wiki: improve quality for important tips to improve the quality of your input image.

The awesome magick R package has many useful functions that can be use for enhancing the quality of the image. Some things to try:

  • If your image is skewed, use image_deskew() and image_rotate() make the text horizontal.
  • image_trim() crops out whitespace in the margins. Increase the fuzz parameter to make it work for noisy whitespace.
  • Use image_convert() to turn the image into greyscale, which can reduce artifacts and enhance actual text.
  • If your image is very large or small resizing with image_resize() can help tesseract determine text size.
  • Use image_modulate() or image_contrast() or image_contrast() to tweak brightness / contrast if this is an issue.
  • Try image_reducenoise() for automated noise removal. Your mileage may vary.
  • With image_quantize() you can reduce the number of colors in the image. This can sometimes help with increasing contrast and reducing artifacts.
  • True imaging ninjas can use image_convolve() to use custom convolution methods.

Below is an example OCR scan from an online AI course. The code converts it to black-and-white and resizes + crops the image before feeding it to tesseract to get more accurate OCR results.


Linking to ImageMagick
Enabled features: freetype
Disabled features: cairo, fontconfig, fftw, ghostscript, lcms, pango, rsvg, webp, x11
input <- image_read("")

text <- input %>%
  image_resize("2000x") %>%
  image_convert(type = 'Grayscale') %>%
  image_trim(fuzz = 40) %>%
  image_write(format = 'png', density = '300x300') %>%

The Life and Work of
Fredson Bowers

plishment and influence cause them to be the symbols of their age;
their careers and oeuvres become the touchstones by which the
field is measured and its history told. In the related pursuits of
analytical and descriptive bibliography, textual criticism, and scholarly
editing, Fredson Bowers was such a figure, dominating the four decades
after 1949, when his Principles of Bibliographical Description was pub-
lished. By 1973 the period was already being called “the age of Bowers”:
in that year Norman Sanders, writing the chapter on textual scholarship
for Stanley Wells's Shakespeare: Select Bibliographies, gave this title to
a section of his essay. For most people, it would be achievement enough
to rise to such a position in a field as complex as Shakespearean textual
studies; but Bowers played an equally important role in other areas.
Editors of nineteenth-century American authors, for example, would
also have to call the recent past “the age of Bowers," as would the writers
of descriptive bibliographies of authors and presses. His ubiquity in
the broad field of bibliographical and textual study, his seemingly com-
plete possession of it, distinguished him from his illustrious predeces-
sors and made him the personification of bibliographical scholarship in

his time.

\Vhen in 1969 Bowers was awarded the Gold Medal of the Biblio-
graphical Society in London, John Carter’s citation referred to the
Principles as “majestic," called Bowers's current projects “formidable,"
said that he had “imposed critical discipline" on the texts of several
authors, described Studies in Bibliography as a “great and continuing
achievement," and included among his characteristics "uncompromising
seriousness of purpose” and “professional intensity." Bowers was not
unaccustomed to such encomia, but he had also experienced his share of
attacks: his scholarly positions were not universally popular, and he
expressed them with an aggressiveness that almost seemed calculated to

Read from PDF files

If your images are stored in PDF files they first need to be converted to a proper image format. We can do this in R using the pdf_convert function from the pdftools package. Use a high DPI to keep quality of the image.

pngfile <- pdftools::pdf_convert('', dpi = 600)
Converting page 1 to ocrscan_1.png... done!
text <- tesseract::ocr(pngfile)
TELEPHONE BOOLE (94513) 51617 - TBLEX 123456

Our Ref. 350/PJC/EAC 18th January, 1972.
Dr. P.N. Cundall,
Mining Surveys Ltd.,
Holroyd Road,
Dear Pete,

Permit me to introduce you to the facility of facsimile

In facsimile a photocell is caused to perform a raster scan over

‘ the subject copy. The variations of print density on the document
-cause the photocell to generate an analogous electrical video signal.
This signal is used to modulate a carrier, which is transmitted to a
remote destination over a radio or cable communications link.

At the remote terminal, demodulation reconstructs the video
signal, which is used to modulate the density of print produced by a
printing device. This device is scanning in a raster scan synchronised
with that at the transmitting terminal. As a result, a facsimile
copy of the subject document is produced.

Probably you have uses for this facility in your organisation.

Yours sincerely,
f: (.
Group Leader - Facsimile Research
Registered in England: No. 2038
N0. 1 Registered Office: 80 Views Lune, Ilford. Euex.

Tesseract Control Parameters

Tesseract supports hundreds of control parameters which alter the OCR engine. Use tesseract_params() to list all parameters with their default value and a brief description. It also has a handy filter argument to quickly find parameters that match a particular string.

# List all parameters with *colour* in name or description
# A tibble: 3 x 3
  param                      default desc                    
* <chr>                      <chr>   <chr>                   
1 editor_image_word_bb_color 7       Word bounding box colour
2 editor_image_blob_bb_color 4       Blob bounding box colour
3 editor_image_text_color    2       Correct text colour     

One powerful parameter is tessedit_char_whitelist which restricts the output to a limited set of characters. This may be useful for reading for example numbers such as a bank account, zip code, or gas meter.


numbers <- tesseract(options = list(tessedit_char_whitelist = "$.0123456789"))
cat(ocr("", engine = numbers))

To test if this actually works, look what happens if we remove the $ from tessedit_char_whitelist:

# Do not allow any dollar sign 
numbers2 <- tesseract(options = list(tessedit_char_whitelist = ".0123456789"))
cat(ocr("", engine = numbers2))

Notice how this forces tesseract to detect a number (3 or 8 or 5) if we rule out the dollar sign.

A config file is simply a text file parameters, one name and value per line. You can load config files from your current working directory, or load one of the standard tesseract config files from the tessdata directory.