Yuhimo vs Obsidian

You have notes to keep and knowledge to remember. The useful Yuhimo vs Obsidian question is which of those jobs cannot be optional: a local linked Markdown vault, or built-in page-level learning.

Obsidian is the better local knowledge base. Notes are Markdown files in a vault folder you control. Links, backlinks, and a graph are core capabilities. Native desktop and mobile apps work on those files without an account. Spaced repetition is not a core plugin. If you want a review queue, you add a community plugin that can schedule flashcards or entire notes.

Yuhimo is the better fit when selected pages should return for review as a native notes workflow. Pages stay ordinary notes until you turn learning on. A review grades the page as a whole. Questions are optional recall prompts, not independently scheduled cards.

Yuhimo is our product. That does not make it the default winner.

Stay with Obsidian if the vault is the capability you refuse to give up — including when a plugin, or a smaller subset of notes, already covers the review habit. Choose Yuhimo if built-in page review is the capability you refuse to assemble yourself, and you do not need a local Markdown vault. Choose neither if you need Anki-style atomic drilling or a shared team wiki. There is no universal winner.

Do not migrate a working vault for a review habit a plugin could already handle.

If you are choosing among notes-plus-SRS apps rather than vault versus built-in learning, see Yuhimo vs RemNote. For a broader menu that includes Obsidian-with-plugin among other tools, see Anki alternatives for notes.

Quick comparison

What each app actually is

Obsidian is a local Markdown knowledge base. A vault is a folder of files on a device you control. You connect notes with wikilinks, inspect backlinks, and open a graph of those links. Graph view, Backlinks, and Canvas ship as core plugins and can be disabled. The official product is native desktop and mobile apps, not a browser-first notes service. (How Obsidian stores data, Download)

Yuhimo is a notes app with optional learning. The main object is a page. You can keep a page as an ordinary note forever. Learning is something you turn on for pages you want to retain, not a requirement of writing. Organization is a tree of nested pages, not an outliner with portals and not a graph.

The overlap is real: both store knowledge you might later need to recall. The product difference is not “who has spaced repetition.” It is whether the foundation is a local linked vault, and whether review is a community plugin or a built-in behavior of selected pages.

What gets scheduled

This is the decision that should settle most Yuhimo vs Obsidian comparisons.

Obsidian core does not schedule reviews. Graph view, Backlinks, and Canvas are core plugins. Spaced repetition is not.

A community plugin can add a queue. The widely used Spaced Repetition plugin (st3v3nmw) can schedule flashcards and entire notes. Typical tags such as #flashcards and #review are plugin conventions, not Obsidian syntax. (Spaced Repetition plugin)

In Yuhimo, a learning page is the scheduled unit. You write the page, optionally add questions, then try to reconstruct the topic. After you rate the review, the scheduler updates that page. Questions help you recall it. They do not become independently scheduled cards. Yuhimo does not have a flashcard queue.

The shared study idea is simple: return to important notes after a delay and try to recall before rereading. That does not make either product scientifically proven.

Whole-note plugin review and a Yuhimo learning page can look similar from the chair: a note comes back, you try to recall it, you rate yourself. The difference is built-in versus plugin, not a claim that only Yuhimo can review whole notes. Plugin flashcards are a different object again: independently scheduled cards, not optional prompts on a page. That is the same distinction as spaced repetition without flashcards: retrieval practice does not require a second database of cards.

Neither model is universally better.

A local vault is stronger when the files, links, and graph are the knowledge base, and review is allowed to sit on top. Built-in page scheduling is stronger when the thing you care about is selected notes returning as product behavior, without assembling that path yourself.

Same topic, two workflows

Take how a Git merge conflict is resolved: three-way merge (base, ours, theirs), conflict markers in the file, editing until the result is coherent, then staging and continuing the merge.

Obsidian workflow

You write a note for the procedure. You wikilink related notes — merge vs rebase, the staging area, a branching policy. Backlinks collect every note that points here. Graph view shows the cluster. Canvas can hold a three-way diagram if you want one on a board.

None of that is a review queue. To get one, you enable a community plugin. With Spaced Repetition you might:

• put flashcards in the note so “what do the conflict markers delimit?” can fail on its own schedule;
• or mark the note for whole-note review so the explanation itself returns as one item.

If you keep mixing up base with ours, a card can come back sooner than the rest of the topic. If you tagged the whole note, the next interval belongs to the note. You chose that granularity in the plugin, not in Obsidian core.

Yuhimo workflow

You keep one page for how a conflict is resolved. Surrounding notes — rebase vs merge, team branching rules — can stay as ordinary pages with learning off.

On the conflict page you might add questions such as:

• What does a three-way merge compare?
• What do the conflict markers delimit?
• What still has to happen after you edit the file?

During review you try to reconstruct the procedure, use the prompts if you added them, then grade the page: Forgot, Barely, Remembered, or Easily. Yuhimo trusts that self-assessment. It does not score a typed line against a stored answer. The next interval belongs to that page, not to each prompt. If conflict markers are the weak part, you either edit the page so the next review hits them, or you split that onto its own learning page. The scheduler will not notice the hole for you.

After a page graduates to review, Yuhimo accepts one review grade per calendar day. New pages still in the learning phase can return the same day when a short step is due. Do not flatten that to “you can only ever grade once per day.”

Same subject. Different object of scheduling. Different maintenance: vault plus plugin, or a page with learning turned on.

Notes, files, and questions

In Obsidian, the files are the notes. Leave the app and the Markdown is still there, in a folder you control. Links, tags, and properties live in those files. A plugin can read them and attach a review schedule. Export is not the recovery story; the vault already is.

That is the ownership model people mean when they refuse to give up Obsidian.

Yuhimo export produces readable HTML, TXT, or PDF, and a subtree ZIP in HTML or TXT. Import accepts TXT, DOCX, and HTML. Export is for portability. It is not a vault and not a backup. Scheduling state may not transfer. If restore is the job, that is a different path than “download some files.” See vendor lock-in for what remains readable outside the app.

Do not treat Yuhimo questions as Obsidian plugin flashcards with a different label. In plugin flashcard mode, a card is the review object. In Yuhimo, a question is a cue attached to the page. You do not rate each question. You rate the page after you have used whatever cues you want. That is closer to active recall with notes than to a deck.

Whole-note plugin review is the closer analogue to a learning page. Both bring the note back as one item. One is a community plugin on a local vault. The other is built-in product behavior on hosted pages.

If you need thousands of atomic items — vocabulary, labeled anatomy, formula clozes — a flashcard queue is built for that job. Yuhimo will feel underpowered because optional page questions are not independently scheduled cards. An Obsidian plugin can provide that queue inside the vault. That is still not Obsidian core.

Local vault, links, and graph

Obsidian’s knowledge model is the vault. Daily work is files, wikilinks, unlinked mentions, backlinks, and a graph of those connections. Canvas is a core plugin for spatial boards. You can turn those plugins off. You cannot get the same local-file graph by exporting Yuhimo pages.

Yuhimo’s knowledge model is nested pages. You can outline a topic as a tree. You do not get Obsidian-style backlinks and graph view as the way the product thinks.

If linked local files are how you find and trust your notes, that is not a cosmetic preference. It is the reason to stay with Obsidian even when you also want some notes to return for review.

Built-in learning versus plugin-built learning

Obsidian treats community plugins as optional extensions. Restricted Mode disables them until you turn it off. Community plugins are third-party. They do not auto-update; you choose when to update. That is a maintenance choice, not a claim that any plugin is unsafe. (Community plugins)

Spaced Repetition can schedule flashcards and entire notes. As of v1.15, FSRS is available and is not on by default. Other community plugins also add spaced repetition. This page is not a tour of them.

Yuhimo learning is part of the product. You turn it on per page. There is no Restricted Mode step and no plugin update path for the scheduler. The scheduler is FSRS-light, a lightweight model inspired by spaced repetition. It is not the full official FSRS implementation.

Scheduling models differ in scope, not in a proven memory-percentage gap.

If you already enjoy assembling Obsidian, a plugin is a normal way to add spaced repetition for notes. If you do not want a review system that lives or dies with a third-party plugin, built-in page learning is the other product bet. That is the differentiator. It is not “Yuhimo uniquely reviews whole notes.”

Platforms, offline, and pricing

Obsidian has native apps for Windows, macOS, Linux, iOS, and Android. It is designed to work without internet on local files. Sync is a paid add-on if you want Obsidian to keep vaults in sync across devices. Publish is a paid add-on for hosted notes. The apps themselves do not require an account. (Download, Sync)

Yuhimo is used in the browser as a web app. Offline, you can read cached notes. You cannot edit, grade, start learning sessions, or use AI without a connection.

Obsidian’s app is free to download and use. As of 15 September 2026, Obsidian lists Sync at $4 USD per user per month when billed annually, and Publish at $8 USD per site per month when billed annually. Check Obsidian’s pricing page for current add-ons rather than treating those figures as frozen here.

Yuhimo currently presents signup as free, with no credit card required. Specific paid-plan prices were not clearly published at the time of writing, so this page does not invent one. That is not a promise that the product stays free forever.

Which one should you use?

Decide by which capability cannot be optional, then by what you are willing to maintain. If you want a multi-tool menu rather than this two-name decision, use the Anki alternatives for notes roundup. If the shortlist is notes-plus-SRS apps, use Yuhimo vs RemNote.

Choose Obsidian if

• Local Markdown files are the notes, not an export of the notes.
• Wikilinks, backlinks, and the graph are how you navigate knowledge.
• You want native desktop or mobile apps that work on those files without internet.
• You are willing to add a community plugin for flashcards, whole-note review, or both.
• A review habit on a subset of the vault is enough; the rest can stay unscheduled.

Choose Yuhimo if

• You want a spaced repetition app for notes where the page can stay a page.
• You will leave most notes unscheduled and enable learning only on what you intend to keep.
• You prefer reconstructing a topic, then rating that topic, over maintaining a plugin and a card collection.
• You do not need a local Markdown vault, a graph, or native offline editing.

Stay with Obsidian if

If the vault already works, switching to Yuhimo does not give you a smaller Obsidian. Stay if your notes are local files, if backlinks and the graph are daily tools, or if a plugin already returns the notes you care about. Do not migrate a working vault for a review habit a plugin — or a smaller subset of notes — could cover. Those are fit issues, not a claim that Obsidian is “the better product” in every sense.

When Yuhimo is a poor substitute

Do not switch to Yuhimo to get Obsidian with reviews bolted on. It will not give you:

• a local Markdown vault as the notes themselves;
• wikilinks, backlinks, and graph view as the knowledge model;
• native desktop and mobile apps with offline editing;
• independently scheduled flashcards living in that vault;
• notes that remain readable as local Markdown files if you leave Obsidian.

If those are the reason Obsidian is in your shortlist, Yuhimo is the wrong pairwise answer. Keep the vault. Add a plugin if you need a queue. Or review a subset of notes without moving the rest.

When neither

Choose a flashcard-first tool when the job is drilling a large number of atomic items. The alternatives roundup covers that path; Yuhimo is not a quieter Anki, and Obsidian-with-plugin is still a vault you have to run.

Choose a shared wiki or team workspace when the notes are not a personal vault and not a personal review queue.

There is no universal winner. Obsidian is the better local knowledge base. Yuhimo is the better fit when selected pages should return for review as a native notes workflow. The practical difference is what gets scheduled and which capability you refuse to make optional.