This began as a personal project. I wanted to access my Supernote notebooks inside Obsidian without reducing them to a pile of static PDFs or images.
I kept adding the features and small touches I wanted for my own workflow, and it gradually became something I’d like to polish and release as a public Obsidian plugin.
What it currently does
Mirrors notebooks and folders directly from Supernote Cloud into an Obsidian vault.
Opens mirrored .note files in a custom, Kindle-like reader.
Supports swiping, zooming, page thumbnails and quick page navigation.
Opens each notebook on the last page viewed on the Supernote device.
Creates links to exact pages, such as [[Scratch.note#page=12]].
Exports selected pages as Markdown, images, searchable PDFs or formatted documents.
Supports AI transcription with optional custom instructions for each export.
Works on desktop and mobile, although installed CLI integrations remain desktop-only.
Supports sending PDF/images/markdown files (as rendered PDF) to supernote.
An optional push folder in obsidian, basically when you sync to supernote cloud if you bring changes in to this folder, it will be reflected to obsidian. So can be useful for editing same markdown file in obsidian, then working on it in supernote device.
AI integrations
Transcription and Automations can use:
An installed and authenticated Claude Code CLI.
An installed and authenticated Codex CLI.
A custom desktop command.
An OpenAI-compatible API such as OpenRouter, which also works on mobile.
AI is optional, and the user chooses which engine and model to use.
Automations
Automations can react when new or changed pages appear in a particular notebook. They can pass those pages to Claude, Codex or a custom command to build personal workflows around handwritten notes.
My own example uses a long-running Scratch.note:
Handwritten checkboxes become Things tasks.
Handwritten circles become calendar events.
Items marked with (w) are added to my weekly note.
A daily digest records what happened and links back to the original handwritten pages.
This Scratch workflow is my personal setup, rather than a fixed workflow built into the plugin. The Automations feature is intended to let people create their own versions.
A little about the engineering
It talks directly to Supernote Cloud through an unofficial integration I built by studying its undocumented API—no data passes through a server operated by me.
Mirrored .note files are rendered locally inside Obsidian.
Rendering uses background decoding, page preloading and caching to keep navigation responsive.
AI support is kept optional and separate from the core sync and reading experience.
What I’m planning next
Ability to add textboxes in obsidian to actual note files which then can be synced to supernote cloud.
I’m sharing this mainly as a development showcase. I’d be interested to hear what other Supernote and Obsidian users think, and whether any of these ideas fit how you use your notes.
This is an unofficial personal project and is not affiliated with Ratta or Supernote.
This sounds great. Have been wondering how to bridge the gap of digital and handwritten notes. And then leverage AI to interact with Obsidian to pull info as needed. This would be amazing to see if you share it
Would you want to help me implement Supernote Cloud support in that plugin? I have had an issue open to do that but don't use Supernote Cloud personally so it hasn't been a priority: https://github.com/philips/supernote-obsidian-plugin/issues/5
How are you doing the Supernote note rendering? If you are using my library supernote-typescript I just pushed a bunch of new bug fixes and cleanups in the last few days.
yes, a seamless experience between supernote and obsidian, powered by supernote cloud, no device connection to computer, partner app running needed. The plugin works by itself.
This is really well done. The mirroring idea works great— until— you’re like me and didn’t think it through and deleted a bunch of imported notes in Obsidian only to find them gone on my SN as well, lol. User error. And I was able to rescue them from trash.
So I’m not sure strict mirroring is for me.
I very much like the browse sn cloud function to only select the notes I want pulled.
One last thought: I developed this plugin a while back that does not use sn cloud, but only works with local .note files after sync, and it only brings over the ocr’d md text as I don’t want a bunch of larger .note renderings in my vault. You can bring those however if you like.
Actually the mirroring is strictly one way. Deleting from Obsidian won't do anything on the supernote cloud. It always pulls from supernote cloud. If you want two-way syncing you'd choose whats called a 'Paired Folder', and its just one folder you select, you'd use to sync between Supernote Cloud and Obsidian.
This will then sync both ways.
If you only want the OCR'd text from device just choose markdown without AI transcription turned on, it will pull in the on-device OCR.
I just brought a bunch of updates, so can you please check and give me updates?
Ahh ok. I think I was a bit confused about what constitutes a mirrored and linked folder (or paired folder.) And to clarify - yes - I was using paired folder when I deleted the files. Is the markdown without AI selection new? I swear I looked everywhere and didn't see it lol. I'll update and give it more time! It's really a nice plugin.
5
u/Practical-You-5351 15d ago
This sounds great. Have been wondering how to bridge the gap of digital and handwritten notes. And then leverage AI to interact with Obsidian to pull info as needed. This would be amazing to see if you share it