Handwriting recognition
Handwriting read the way you choose.
To search notes by content and turn them into text, the app reads what you wrote by hand. There are six engines: two run on your Mac with no internet and no keys, four are cloud services on your own key. Which one gets used is up to you.
| Engine | Where it runs | What it needs |
|---|---|---|
| Apple Vision | this Mac | nothing — already in macOS |
| Tesseract | this Mac | a folder of language files |
| Google Cloud Vision | Google’s cloud | an API key |
| Yandex Vision OCR | Yandex’s cloud | an API key |
| MyScript | MyScript’s cloud | an Application Key and an HMAC Key |
| AI model | at a provider | a connection from AI Studio |
Six engines
Who reads your handwriting
the green ones never go online
Apple Vision
this MacBuilt into macOS; needs no setup. Good with Latin and Cyrillic script.
Tesseract
this MacAn open-source engine that runs on your Mac. It keeps languages as separate files — download the ones you need and point it at the folder. Useful for languages Apple doesn’t cover.
Google Cloud Vision and Yandex Vision OCR
cloudCloud services on your own key. Pages go to them as images. At Yandex, handwriting and printed text are read by different models, so the language lists differ.
MyScript
cloudReads the pen strokes themselves rather than a picture of the page, so it works on notebooks, not on scans or PDFs. Handwriting only, on your MyScript Application Key and HMAC Key.
AI model
cloudAny AI model from your AI Studio connections that is marked as able to do OCR. For each one you can allow printed and handwritten text separately — some models read scans well but make things up on handwriting.
Which one reads better depends on your language, your handwriting and the page. We quote no percentages: they would have been measured on somebody else’s handwriting. Try two engines on a note you know well.
Handwriting and print
Two separate choices
a note and a scan are different jobs
The engine and the language are chosen separately for handwriting and for printed text. Each menu lists only the engines that can read that kind of text, and the language list comes from the engine itself.
Spotlight picks no engine of its own: a note goes to the engine you chose for handwriting, a printed PDF to the one you chose for print.
What leaves the Mac
A cloud engine is switched on through a prompt
and off again with one click
Local engines ask for nothing
Apple Vision and Tesseract read on this Mac. Pages go nowhere, so there is nothing to agree to.
Cloud engines are off until you switch them on
Switching one on brings up a prompt: “Page images will leave this Mac and go to Google Cloud Vision with your key.” Cancel leaves the switch off. MyScript gets a notebook’s pen strokes rather than images. Turning the engine off withdraws the consent: switch it on again and it asks again. The choice and the consent follow your settings to your other Macs, so a second Mac doesn’t ask again.
Keys live in the Keychain
Cloud service keys are kept in the macOS Keychain; with iCloud Keychain they reach your other Macs. Privacy →
Formatting by hand
Write Markdown with the pen
a hash for a heading, asterisks for bold
It works with all six engines, MyScript included. In AI Studio it’s a switch on each action; off, the marks stay exactly as you wrote them.
Headings
One to four hashes and a space at the start of a line make a heading, four levels deep.
Bold, italic, struck through
Two asterisks or two underscores around words make them bold, one makes them italic, and two tildes strike them out.
What stays as written
C#, #tag, 2*3, formulas, code and links are left alone, and so is a mark without its pair. When in doubt, the character stays.
Typed text in its place
Text typed on the tablet stands among the handwritten lines, where it is on the page — even with an engine that reads only the handwriting.
Formulas by hand
Handwritten formulas become LaTeX
on by default
A formula written by hand is read by MyScript or by an AI reader among your connections, and typeset in LaTeX wherever the document shows it.
Works with the pen
Read beside the Markdown written by hand, with every engine that can read formulas.
Off for one action
Turn it off with Formulas as LaTeX on that action, and the page keeps the look you wrote instead.
Read once
The result is shared across the app
and never read again
Stored with the document
The text that was read is kept alongside the document’s version and the engine’s name. Search, AI Studio, integrations and MCP take it from there instead of reading again.
A PDF with its own text isn’t recognized
If the file already has a text layer, that is what gets used. Blank notebook pages are skipped as well: out of 50 pages with 11 written on, 11 are read.
A model refused — the pass carries on
One document a model wouldn’t read is flagged and doesn’t hold up the rest. A fallback model on the same connection can pick it up, or you can read it on the Mac with “Read locally.”
What stops the whole pass
Only what is the same for every document: a rejected key, an empty balance, an answer in an unexpected format. The app tells you what happened.
FAQ
Questions about recognition
- Is a document re-read on every search?
- No. What was read is stored and used by every feature. It’s read again only if the document changed or you picked another engine.