Papers › EAST: An Efficient and Accurate Scene Text Detector

EAST: An Efficient and Accurate Scene Text Detector

11 Apr 2017CVPR 2017 7arXiv:1704.03155archive 2025-07-28

Xinyu Zhou, Cong Yao, He Wen, Yuzhi Wang, Shuchang Zhou, Weiran He, Jiajun Liang

Previous approaches for scene text detection have already achieved promising performances across various benchmarks. However, they usually fall short when dealing with challenging scenarios, even when equipped with deep neural network models, because the overall performance is determined by the interplay of multiple stages and components in the pipelines. In this work, we propose a simple yet powerful pipeline that yields fast and accurate text detection in natural scenes. The pipeline directly predicts words or text lines of arbitrary orientations and quadrilateral shapes in full images, eliminating unnecessary intermediate steps (e.g., candidate aggregation and word partitioning), with a single neural network. The simplicity of our pipeline allows concentrating efforts on designing loss functions and neural network architecture. Experiments on standard datasets including ICDAR 2015, COCO-Text and MSRA-TD500 demonstrate that the proposed algorithm significantly outperforms state-of-the-art methods in terms of both accuracy and efficiency. On the ICDAR 2015 dataset, the proposed algorithm achieves an F-score of 0.7820 at 13.2fps at 720p resolution.

PaperPDFConference PDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

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

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 6 code samples harvested from 4 repositories linked to this paper: 5 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 5 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

By repository: community (archive-listed): 6 samples from 4 repositories, 5 ran (0 with no instrument failure; 5 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

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

Antika-Roy/TextDetectionAndRecognition mentioned on GitHubSyntology: not harvested report
BruceChanJianLe/Image-Text-Recognition mentioned on GitHubSyntology: not harvested report
CCLDArjun/Arjun-EAST mentioned on GitHubpytorchSyntology: not harvested report
Chris10M/RFB-Text-Detection mentioned on GitHubtfSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
GokulKarthik/EAST.pytorch mentioned on GitHubpytorchSyntology: not harvested report
Kaushal28/FOTS-PyTorch mentioned on GitHubpytorchSyntology: not harvested report
Mind23-2/MindCode-35 mentioned on GitHubmindsporeSyntology: not harvested report
PaddlePaddle/PaddleOCR mentioned on GitHubpaddleApache-2.0Syntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to KRETA: A Benchmark for Korean Reading and Reasoning in Text-Rich VQA Attuned to... (arXiv:2508.19944; that paper's own run record: 6 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 3 violated, 0 with no contract checked; 3 where Syntology's instrument failed) · 2 unverified); nothing checks that they implement this paper's method. report
Tanmaiyee28/Python-Project-Street-View-text-detection mentioned on GitHubSyntology: not harvested report
ZXdatascience/TextDetectorAndroid mentioned on GitHubSyntology: not harvested report
alililia/ascend_advanced_east mentioned on GitHubmindsporeSyntology: not harvested report
argman/EAST mentioned on GitHubtfSyntology: 1 sample, 0 ran · 1 unverified report
dengdan/seglink mentioned on GitHubtfSyntology: not harvested report
ingbeeedd/EAST-tf2keras mentioned on GitHubtfSyntology: not harvested report
isaacaddis/Seung mentioned on GitHubSyntology: not harvested report
jnkl314/tin_dr mentioned on GitHubSyntology: not harvested report
kurapan/EAST mentioned on GitHubtfSyntology: not harvested report
liushuchun/EAST.pytorch mentioned on GitHubpytorchSyntology: not harvested report
owseaman/Text-Detection-in-an-Image mentioned on GitHubSyntology: not harvested report
solaris33/EAST-tf2 mentioned on GitHubtfSyntology: not harvested report
swapnamoy17/EAST-DenseNet mentioned on GitHubtfSyntology: not harvested report
yakhyo/east-pytorch mentioned on GitHubpytorchSyntology: 2 samples, 2 ran (2 instrument-failed) · 0 unverified report
zahrakhoshdel/realtime-text-detection-and-recognition mentioned on GitHubSyntology: not harvested report
zxytim/EAST mentioned on GitHubtfSyntology: not harvested report
zyasjtu/EAST mentioned on GitHubtfSyntology: not harvested report
2023-MindSpore-4/Code3 mindsporeSyntology: not harvested report
Mind23-2/MindCode-5 mindsporeSyntology: not harvested report
SakuraRiven/EAST pytorchSyntology: 2 samples, 2 ran (2 instrument-failed) · 0 unverified report
mindspore-lab/mindocr mindsporenot reachable when probed 2026-09-17 — repositories for recent papers often appear after camera-readySyntology: not harvested 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

6 samples harvested: 5 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 5 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

3ran · our draft was wrong
2ran; the contract check could not run
1unverified

Licence: 1 of the 6 samples is 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 4 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (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 are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. 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 six 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; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. 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.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

Chris10M/RFB-Text-Detection community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
get_path_list run_demo.py ran · our draft was wrong MIT (permissive) · 2810b57a93d7c863 · report fixture: signature root_path:str/0/str · returned list · level recorded 2026-09-22
argman/EAST community (archive-listed) 1 sample, 0 ran · 1 unverified
get_predictor in 19 papers run_demo_server.py unverified GPL-3.0 (copyleft) · pointer only · 85d1fadaaf9cb100 · report
yakhyo/east-pytorch community (archive-listed) 2 samples, 2 ran (2 instrument-failed) · 0 unverified
is_valid_poly detect.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic MIT (permissive) · d683e0b7226e6e35 · report fixture: signature res:ndarray/2/float, score_shape:tuple/1/int, scale:int/0/int · returned bool · level recorded 2026-09-22
resize in 108 papers
census: 10 implementations from 14 papers, 5 distinct outputs across 2 buckets, one shared input per bucket
detect.py ran · our draft was wrong MIT (permissive) · e55b33eadf6b16e5 · report fixture: signature image:Image/0/? · returned tuple · level recorded 2026-09-22
SakuraRiven/EAST community (archive-listed) 2 samples, 2 ran (2 instrument-failed) · 0 unverified
is_valid_poly detect.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic MIT (permissive) · 66e30af743cc4a1a · report fixture: signature res:ndarray/2/float, score_shape:tuple/1/int, scale:int/0/int · returned bool · level recorded 2026-09-22
resize_img in 31 papers detect.py ran · our draft was wrong MIT (permissive) · 31e0255b8c515ebb · report fixture: signature img:Image/0/? · returned tuple · level recorded 2026-09-22

Tasks

Curved Text DetectionOptical Character Recognition (OCR)Scene Text DetectionText Detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Scene Text Detection COCO-Text EAST + VGG16 F-Measure 39.45 #3 of 6 Archive leaderboard report
Scene Text Detection COCO-Text EAST + VGG16 Precision 50.39 #3 of 6 Archive leaderboard report
Scene Text Detection COCO-Text EAST + VGG16 Recall 32.4 #3 of 6 Archive leaderboard report
Scene Text Detection ICDAR 2015 PAN F-Measure 82.9 #33 of 43 Archive leaderboard report
Scene Text Detection ICDAR 2015 PAN Precision 84 #33 of 43 Archive leaderboard report
Scene Text Detection ICDAR 2015 PAN Recall 81.9 #33 of 43 Archive leaderboard report
Scene Text Detection ICDAR 2015 EAST + PVANET2x RBOX (single-scale) F-Measure 78.2 #37 of 43 Archive leaderboard report
Scene Text Detection ICDAR 2015 EAST + PVANET2x RBOX (single-scale) Precision 83.6 #37 of 43 Archive leaderboard report
Scene Text Detection ICDAR 2015 EAST + PVANET2x RBOX (single-scale) Recall 73.5 #37 of 43 Archive leaderboard report
Scene Text Detection MSRA-TD500 EAST + PVANET2x F-Measure 76.08 #18 of 18 Archive leaderboard report
Scene Text Detection MSRA-TD500 EAST + PVANET2x Precision 87.28 #18 of 18 Archive leaderboard report
Scene Text Detection MSRA-TD500 EAST + PVANET2x Recall 67.43 #18 of 18 Archive leaderboard report
Scene Text Detection Total-Text EAST F-Measure 42.0% #26 of 27 Archive leaderboard report
Scene Text Detection Total-Text EAST Precision 50.0 #26 of 27 Archive leaderboard report
Scene Text Detection Total-Text EAST Recall 36.2 #26 of 27 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