Standard Notes Import moves decrypted backups into Markdown notes

Name: Standard Notes Import
Author: theluckystrike

Import supported text, tags, UUIDs and dates from a decrypted JSON backup.

Install in Obsidian

Directory page Source on GitHub

MIT · no telemetry · core features free

An imported trip note shows its source UUID, original title, tags and date properties. — Open larger

version: 1.2.0
released: 2026-10-21
downloads: 38
review: Passed
health: Excellent
license: MIT
listed for: Desktop, Mobile
obsidian: 1.13.4 or later

The review tested the desktop app on macOS. No physical phone or tablet test ran.

Directory facts fetched 2026-10-23 07:28 UTC from community.obsidian.md/users/theluckystrike.

About Standard Notes Import

You want to move supported plain text or Markdown records from a Standard Notes backup into your vault.

Standard Notes Import reads a decrypted JSON backup with a .json or .txt extension in your vault. Check proposed paths and skipped records before creating Markdown notes with source properties. Existing notes keep their text.

Pro saves destination folders by source tag and previews changed records on a repeat import. That preview helps you review differences; it doesn't merge updates.

The demo shows backup selection, a report and an imported sample note.

Free features

Choose a decrypted backup

Choose a decrypted JSON backup with a .json or .txt extension in your vault. Check backup lists planned paths without creating notes. The parser accepts an items array with no version field or version 004.

The import dialog shows a sample JSON backup and destination folder controls. — Open larger

Import the native text backup

Extract a decrypted ZIP first, then select Standard Notes Backup and Import File.txt from your vault without renaming it. The file must contain JSON with an items array. Individual text notes and ZIP files cannot be imported.

The import dialog selects the original Standard Notes text backup. — Open larger

Keep text and join source tags

Supported plain text and Markdown records keep their body text. The importer joins Tag-to-Note and Note-to-Tag references, removes repeated tag names and skips deleted tags. Original names stay in source_tags, while converted tags go in tags.

The backup check shows work and travel tags beside three planned note paths. — Open larger

Keep titles and source dates

Properties keep the original title, UUID and source tags. Supplied creation and update date strings become source properties, rather than file system dates. File paths use a cleaned title and the full source UUID.

Read skipped records and conflicts

The report lists unsupported editors, encrypted content, malformed records, missing tag references, duplicate UUIDs and path conflicts. A UUID found in a vault note causes a skip, including after you rename or move that note. Write errors name the affected path, and earlier created notes remain.

The report lists encrypted content, an unsupported editor and UUIDs already in the vault. — Open larger

The free importer has no note count limit, but format checks still restrict which records it can read.

Pro features

Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.

Save destination rules by tag Pro

Save rules such as work => Imported/Work in the plugin settings. Source tag names are case sensitive, and the first matching rule chooses the folder. Without Pro, the rules stay saved but imports use the default destination.

The settings show saved work and travel folder rules beside sample Pro account controls. — Open larger

Preview changed records Pro

Pro compares matching UUIDs and shows existing and incoming text, titles, source tags and dates. Local body edits can appear as changes too. The preview writes no notes and doesn't replace or move existing records.

An expanded changed record shows existing vault text beside incoming backup text. — Open larger

See how Pro works

Set up Standard Notes Import

needs

Obsidian 1.13.4 or later
A decrypted legacy or version 004 JSON backup with a .txt or .json extension inside your vault.

steps

Export a decrypted Standard Notes backup, extract its ZIP if needed and keep a separate copy.
Copy the .txt or .json backup into your vault and run Import a decrypted backup.
Choose the file and destination, then select Check backup.
Read planned paths and skipped records, then close the report.
Select Import notes and check the new Markdown files and source properties.

If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.

How to import Standard Notes into Obsidian

Known limits of Standard Notes Import

The importer reads a decrypted JSON backup with an items array and either no version field or version 004.
Note UUIDs must contain 1 to 80 ASCII letters, digits or hyphens.
Supported editor identifiers are com.standardnotes.plain-text and org.standardnotes.simple-markdown-editor; other identifiers are skipped.
A supplied noteType must be plain-text or markdown, even when the editor identifier is absent.
Encrypted content, rich editor conversion and attachment downloads are outside this version.
Repeat imports skip UUIDs already in vault notes; the Pro preview does not merge, replace or move those notes.
Removing source_uuid can make a record appear new, though an occupied output path can still block it.
Source date strings become properties rather than file system dates.
Write failures leave earlier created notes in place, and there is no undo command.
Physical mobile devices, Linux app runs, large private backups and device synchronization conflicts remain untested.

Questions about Standard Notes Import

Can it decrypt an encrypted backup?

No. The importer needs a decrypted JSON backup, and it skips encrypted string content with a report message. It doesn't handle encryption keys.

Which note editors can it read?

It supports plain text without an editor identifier and the identifiers com.standardnotes.plain-text and org.standardnotes.simple-markdown-editor. A supplied noteType must be plain-text or markdown. Other editors and note types are skipped; rich editor conversion and attachment downloads are outside this version.

Why does my changed note get skipped on a repeat import?

The source UUID identifies a record already imported, so the importer leaves its vault note unchanged. Pro shows differences for manual review. It doesn't merge updates.

Do I need an account to import?

No. The free importer works without signing in. GitHub sign-in checks sponsorship for the saved tag rules and changed-record preview.

Network use

Sign-in sends the client ID and device codes to github.com; api.github.com receives your token and a sponsorship query, without vault data. Successful Pro checks wait seven days; failed checks can retry after six hours, and Refresh checks when you're signed in. The plugin sends no requests before you start GitHub sign-in.

Read the full network disclosure

Questions or ideas?

Tell me what is broken in Standard Notes Import, or what it should do next.

Send feedback

Standard Notes Import 1.2.0, MIT license