# ABBYY OCR Layout Detection is Broken in DEVONthink

**URL:** https://discourse.devontechnologies.com/t/abbyy-ocr-layout-detection-is-broken-in-devonthink/80787
**Category:** Feedback
**Tags:** devonthink3, bug-report
**Created:** [September 18, 2024, 10:34pm UTC](https://discourse.devontechnologies.com/t/abbyy-ocr-layout-detection-is-broken-in-devonthink/80787 "2024-09-18T22:34:49Z")
**Posts on this page:** 1
**Showing post:** 17

<div class="post-metadata">

### Author: ![SebMacV](https://discourse.devontechnologies.com/letter_avatar_proxy/v4/letter/s/85e7bf/32.png) [@SebMacV](https://discourse.devontechnologies.com/u/SebMacV)
#### Post date: [September 27, 2024, 5:15am UTC](https://discourse.devontechnologies.com/t/abbyy-ocr-layout-detection-is-broken-in-devonthink/80787/17 "2024-09-27T05:15:09Z")

</div>

Glad to hear that ABBYY sits at the top.

I think that there are many use cases for the in-built OCR that serve folks just fine (OCRing scanned receipts, bank statements, etc for search purposes). You (and I) have bespoke PDF requirements, work intensively with text to produce professional outputs, and so need high levels of accuracy. We are no stranger to software workaround to get to our desires workflows and outputs. Despite my grumble note above (directed more at the inherent problems of PDF rather than at DT’s ABBYY implementation), I would still wholeheartedly recommend the Pro Edition to my doctoral students. There are other distinguishing features, too, that may be critical for ‘pro’ workflows: see [DEVONThink standard vs DEVONThink Pro - #7 by pete31](https://discourse.devontechnologies.com/t/devonthink-standard-vs-devonthink-pro/59048/7); and here [DEVONtechnologies | DEVONthink Editions](https://www.devontechnologies.com/apps/devonthink/editions)

As they say, YMMV 🙂

---

_[View the full topic](https://discourse.devontechnologies.com/t/abbyy-ocr-layout-detection-is-broken-in-devonthink/80787)._