Dropbox builds in-house deep learning OCR pipeline for mobile document scanner
Dropbox's commercial off-the-shelf OCR SDK was expensive (charged per scan) and tuned for flat-bed scanners, not mobile photos with crinkled documents, shadows, and uneven lighting; Dropbox also lacked control over future innovation.
When the Word Detector and Word Deep Net were first chained end-to-end, accuracy dropped to around 44%—far below the competition—due to spacing errors and spurious garbage text from image noise.
After about 8 months of research, productionization, and refinement, Dropbox deployed a state-of-the-art OCR pipeline to millions of Dropbox Business users, achieving mid-90s Single Word Accuracy and replacing the commercial SDK entirely.
Show all 6 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
After about 8 months of research, productionization, and refinement, Dropbox deployed a state-of-the-art OCR pipeline to millions of Dropbox Business users, achieving mid-90s Single Word Accuracy and replacing the com…
What tools did this team use?
TensorFlow, OpenCV, Torch, Amazon EC2 G2, S3, Stormcrow, DropTurk, Mechanical Turk, LXC, Inception Resnet v2.
What results were reported?
Single Word Accuracy after initial synthetic training: around 79%; Single Word Accuracy after fine-tuning on real images: mid-90s; Initial end-to-end accuracy: 44%; deployment coverage of Dropbox Business users: 100% (source-reported, not independently verified).
What failed first in this deployment?
When the Word Detector and Word Deep Net were first chained end-to-end, accuracy dropped to around 44%—far below the competition—due to spacing errors and spurious garbage text from image noise.
How is this data entry ops AI workflow structured?
Mobile document upload → Orientation detection → Word Detector segments image → Word Deep Net recognizes text → Confidence scoring and lexicon validation → Wordinator post-processing → PDF hidden layer and search index.