Papers › Multi-digit Number Recognition from Street View Imagery using Deep Convolutional...

Multi-digit Number Recognition from Street View Imagery using Deep Convolutional Neural Networks

20 Dec 2013arXiv:1312.6082archive 2025-07-28

Ian J. Goodfellow, Yaroslav Bulatov, Julian Ibarz, Sacha Arnoud, Vinay Shet

Recognizing arbitrary multi-character text in unconstrained natural photographs is a hard problem. In this paper, we address an equally hard sub-problem in this domain viz. recognizing arbitrary multi-digit numbers from Street View imagery. Traditional approaches to solve this problem typically separate out the localization, segmentation, and recognition steps. In this paper we propose a unified approach that integrates these three steps via the use of a deep convolutional neural network that operates directly on the image pixels. We employ the DistBelief implementation of deep neural networks in order to train large, distributed neural networks on high quality images. We find that the performance of this approach increases with the depth of the convolutional network, with the best performance occurring in the deepest architecture we trained, with eleven hidden layers. We evaluate this approach on the publicly available SVHN dataset and achieve over 96% accuracy in recognizing complete street numbers. We show that on a per-digit recognition task, we improve upon the state-of-the-art, achieving 97.84% accuracy. We also evaluate this approach on an even more challenging dataset generated from Street View imagery containing several tens of millions of street number annotations and achieve over 90% accuracy. To further explore the applicability of the proposed system to broader text recognition tasks, we apply it to synthetic distorted text from reCAPTCHA. reCAPTCHA is one of the most secure reverse turing tests that uses distorted text to distinguish humans from bots. We report a 99.8% accuracy on the hardest category of reCAPTCHA. Our evaluations on both tasks indicate that at specific operating thresholds, the performance of the proposed system is comparable to, and in some cases exceeds, that of human operators.

PaperPDFCodeCode Syntology ran

In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="1312.6082")

Code

Syntology Ran 2 of 6 code samples harvested from 3 repositories linked to this paper; 4 have no recorded run. Of those that ran: 1 ran · our draft was wrong; 1 ran · fixture could not drive it.

By repository: community (archive-listed): 6 samples from 3 repositories, 2 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

17 repositories listed; official and paper-mentioned ones first.

GurpartapSS/anpr_CNN mentioned on GitHub report
JennyVanessa/Paddle-SVHN mentioned on GitHubpaddle report
Pek20180909/SVHN mentioned on GitHubtfMIT report
ap3885/street_view_imagery mentioned on GitHubtf report
beeps82/SVHN_CNN mentioned on GitHubtf report
lixilinx/MCMIL mentioned on GitHubpytorch report
mimikaan/Attention-Model mentioned on GitHubtfMIT report
ms5898/e4040-2019fall-project mentioned on GitHubtf report
nikola310/svhn_classification mentioned on GitHubGPL-3.0 report
titulacion2021/Image-Classification-ResNet mentioned on GitHubtfNOASSERTION report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

6 samples harvested; 2 ran; 0 honoured the contract we drafted; 4 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

1ran · our draft was wrong
1ran · fixture could not drive it
4unverified

Licence: 3 of the 6 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 3 repositories linked to this paper, official or community; each sample names its own and says which. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

get_lr_metric beeps82/SVHN_CNN/final_runv3.py community (archive-listed) ran · our draft was wrong no licence file found · pointer only · bd9deb72fd95c9ae · report
new_accuracy beeps82/SVHN_CNN/final_runv3.py community (archive-listed) ran · fixture could not drive it fingerprinted no licence file found · pointer only · c3f32e94cdacfaf7 · report
gauss Factotum8/test_task_street_view_house_numbers/CNN_eval.py community (archive-listed) unverified MIT (permissive) · c1f2fbdbe5cfa21f · report
gaussian_filter Factotum8/test_task_street_view_house_numbers/CNN_eval.py community (archive-listed) unverified MIT (permissive) · cb97dd4d6528d2bd · report
gaussian_filter_ Factotum8/test_task_street_view_house_numbers/CNN_eval.py community (archive-listed) unverified MIT (permissive) · efb7bd6cbcb8bf60 · report
infer_best_match ahmad0790/svhn-multi-digit-address-recognition/predictions.py community (archive-listed) unverified no licence file found · pointer only · 8fb0900a352c2e0b · report

Tasks

Image Classification

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Image Classification SVHN DCNN Percentage error 2.2 #29 of 62 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections