# Ability to edit OCR for a note

**URL:** <https://discourse.joplinapp.org/t/ability-to-edit-ocr-for-a-note/44181>\
**Category:** Features\
**Created:** [4 March 2025 16:28 UTC](https://discourse.joplinapp.org/t/ability-to-edit-ocr-for-a-note/44181 "2025-03-04T16:28:40Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![weaver](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/weaver/32/24618_2.png) [@weaver](https://discourse.joplinapp.org/u/weaver)\
**Post date:** [4 March 2025 16:28 UTC](https://discourse.joplinapp.org/t/ability-to-edit-ocr-for-a-note/44181/1 "2025-03-04T16:28:40Z")

</div>

When an image is right clicked and "View OCR Text" is selected, a file under `/tmp` is opened with the OCRed text in TextEdit (at least on Mac.)

I can make edits to this file and save it in TextEdit, but Joplin does not read it. Joplin should read any edits I make to this file and update the OCR text attached to an image.

---

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [4 March 2025 16:57 UTC](https://discourse.joplinapp.org/t/ability-to-edit-ocr-for-a-note/44181/2 "2025-03-04T16:57:53Z")

</div>

We're considering adding the OCR text directly to the note, which would make it editable. I don't know if it's a good idea to add the OCR text to the note or not though

---

<div class="post-metadata">

**Author:** ![weaver](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/weaver/32/24618_2.png) [@weaver](https://discourse.joplinapp.org/u/weaver)\
**Post date:** [4 March 2025 17:20 UTC](https://discourse.joplinapp.org/t/ability-to-edit-ocr-for-a-note/44181/3 "2025-03-04T17:20:09Z")

</div>

What about a button on each image that would copy the text into the note? Then it could be opt-in for users who want it.

Additionally, you could add a checkbox in the settings to automatically always copy text into a note.

---

<div class="post-metadata">

**Author:** ![JackGruber](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/jackgruber/32/3231_2.png) [@JackGruber](https://discourse.joplinapp.org/u/JackGruber)\
**Post date:** [4 March 2025 17:44 UTC](https://discourse.joplinapp.org/t/ability-to-edit-ocr-for-a-note/44181/4 "2025-03-04T17:44:32Z")

</div>

I don't like this. In a seperated field ok, but not in the note itself. Also not on export of a note. I have so many files in Notes, the OCR Text of the files would mess up the notes and is not directly releated to a Note.

---

<div class="post-metadata">

**Author:** ![HarSel](https://yyz2.discourse-cdn.com/flex028/user_avatar/discourse.joplinapp.org/harsel/32/13486_2.png) [@HarSel](https://discourse.joplinapp.org/u/HarSel)\
**Post date:** [4 March 2025 21:25 UTC](https://discourse.joplinapp.org/t/ability-to-edit-ocr-for-a-note/44181/5 "2025-03-04T21:25:16Z")

</div>

As part of an image it has context. As part of the note it could be very bad if added automatically.

---

<div class="post-metadata">

**Author:** ![laurent](https://avatars.discourse-cdn.com/v4/letter/l/ce7236/32.png) [@laurent](https://discourse.joplinapp.org/u/laurent)\
**Post date:** [5 March 2025 00:16 UTC](https://discourse.joplinapp.org/t/ability-to-edit-ocr-for-a-note/44181/6 "2025-03-05T00:16:43Z")

</div>

Yes that makes sense, that's a bit my feeling too actually. I want to improve the access to this OCR data but I guess the data model itself is fine - the OCR text being associated with the resource.

But it's probably it terms of UI that we need to improve this, just to make it (optionally) more visible.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex028/uploads/cozic/original/3X/1/c/1c948e33314e232a0927789508474d8624f4270b.png) [@system](https://discourse.joplinapp.org/u/system)\
**Post date:** [28 February 2026 00:17 UTC](https://discourse.joplinapp.org/t/ability-to-edit-ocr-for-a-note/44181/7 "2026-02-28T00:17:21Z")

</div>

This topic was automatically closed 360 days after the last reply. New replies are no longer allowed.