OPML Note Import turns outline roots into Markdown notes

Name: OPML Note Import
Author: theluckystrike

Import OPML roots as notes with nested items in source order.

Install in Obsidian

Directory page Source on GitHub

MIT · no telemetry · core features free

A Launch plan outline preview with nested items and notes. — Open larger

version: 1.2.0
released: 2026-10-21
downloads: 42
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 OPML Note Import

You have an OPML outline export and want separate Markdown notes for its root items.

OPML Note Import creates one Markdown note for each root outline item. Child items become nested lists, and item notes stay beneath their outline text. Preview the proposed paths and note text before you import.

Your source stays in place, and the import skips existing output paths. Pro saves named layouts and compares planned Markdown with notes at those paths.

The demo selects a sample outline, previews its roots and shows the import result.

Free features

Select a local outline

Choose an .opml file already in your vault, a destination folder and an optional filename prefix. The importer reads the file locally without connecting to the outline tool. Source properties can add the source path, root number and source id.

The import dialog shows a sample OPML source and destination controls. — Open larger

Keep nested items and notes

Root items become headings in separate notes, and child lists keep source order and indentation. The parser reads text, note and _note attributes, plus common URL attributes. Escaped HTML stays literal text, and Markdown control characters receive escaping.

Inspect file name conflicts

Preview shows paths before writing, and duplicate cleaned names receive numbered suffixes starting at 2. Case variants count as duplicates. Existing paths are skipped, while a file blocking a destination folder stops the import before writing.

The preview gives a duplicate Launch plan root a numbered filename. — Open larger

Read parse errors

Invalid XML, DOCTYPE and entity declarations stop the plan before note creation. Unknown attribute names appear as warnings; their values aren't converted into note text. The importer doesn't fetch feeds or external entities.

The outline dialog shows an invalid XML error for mismatched tags. — Open larger

Choose the note level

Choose a level from 1 to 6 to make one note per outline item at that depth. Use level 2 or higher when one root item contains your whole outline. The preview reports branches that end above your chosen level and parent items whose note text or URLs will not import.

A level 2 preview shows separate notes for dated children of a journal root. — Open larger

Free imports have no paid root count limit; the same parser limits apply with Pro.

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 layouts Pro

Save a named layout with its level, folder, prefix and source property option, then apply it to another outline. The source file stays a separate choice. The plugin keeps up to 50 presets, and saving the same name replaces that preset.

The Pro layout controls show a named Project notes preset. — Open larger

Preview repeated imports Pro

Pro labels destination files new, changed or unchanged and identifies blocking folders. Changed previews show lines found only in planned text or only in existing text. The comparison doesn't update files or find removed roots and moved notes.

The repeat preview shows one changed path and one unchanged path. — Open larger

See how Pro works

Set up OPML Note Import

needs

Obsidian 1.13.4 or later
An OPML outline file inside your vault.

steps

Export your outline as OPML and copy the file into the vault.
Run Import an outline file from the command palette.
Choose the source, note level, destination folder, prefix and source property option.
Select Preview, then expand a root path to inspect its Markdown text.
Select Import notes and read the created, skipped and error paths.

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 OPML outlines into Obsidian

Known limits of OPML Note Import

The source must be an .opml file inside your vault.
The parser rejects input beyond 2,000,000 JavaScript string units, 100 nested XML levels or 10,000 outline items.
DOCTYPE and entity declarations are rejected before XML parsing.
Escaped HTML stays literal text, and unsupported attribute values are not converted.
Feed URLs stay as text; the importer does not download articles, subscribe to feeds or import attachments.
Existing output paths are skipped; the Pro comparison does not update their contents.
Repeat previews compare destination paths and do not find removed roots or notes moved elsewhere.
Source ids use the source path and root position, so root reordering can change them.
The plugin keeps up to 50 named layouts, and saving an existing name replaces its preset.
Storage errors leave earlier created files in the vault.
Physical mobile devices, Windows and Linux app runs, installed outline exporters and interrupted writes on remote storage remain untested.

Questions about OPML Note Import

Can I use a feed subscription export?

The importer keeps outline text and common URL attributes, including xmlUrl. It doesn't download articles, subscribe to feeds or import attachments.

What parser limits apply?

The parser rejects input beyond 2,000,000 JavaScript string units, 100 nested XML levels or 10,000 outline items. These limits apply to free and Pro imports.

Does a repeat import replace my existing notes?

No. Import notes skips existing paths after the comparison. A renamed root appears as a new path, and the preview doesn't find removed roots or notes moved elsewhere.

Does a source id survive root reordering?

No. The source id combines the vault source path and the root's position. Reordering roots can change that id.

Can I read the notes after disabling the plugin?

Yes. The output uses Markdown with optional YAML source properties. The files remain readable and editable without Pro or this plugin.

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 OPML Note Import, or what it should do next.

Send feedback

OPML Note Import 1.2.0, MIT license