Convert ORG to OPML
Turn ORG files into OPML. An OPML outline with one item per heading, nested by level, and the text under each heading as the item's note in Markdown.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop ORG files on the dialor turn it to pick what to do
An outline from your Org file.Each heading becomes an item, nested by level, with its text as a note.
What you get
One OPML file with one item per heading. Items nest by heading level, so the outline matches the structure of the Org file. The text under each heading becomes that item's note, written in Markdown.
Text before the first heading goes into a first item. It is named after #+TITLE, or after the file name if there is no title.
What stays
TODO keywords and tags stay in the headings, so they remain visible in each item's title.
Images become their caption.
What is left out
The conversion follows what an Emacs export leaves out. Source block results, drawers and planning lines are dropped. Headings tagged noexport are dropped too.
Going back
To turn an outline into Org again, use OPML to ORG. For other options, see every ORG conversion.
ORG and OPML.What each format is.
The formats
Org Mode
Org mode, Emacs' outliner and notebook format.
- Extensions
- .org
- MIME type
- text
/x -org - Kind
- Text and data
OPML Outline
OPML outlines, the exchange format of outliners and feed readers.
- Extensions
- .opml
- MIME type
- text
/x -opml - Kind
- Text and data
In your code.The same ORG to OPML conversion through the API, for your app or your agent.
$ cv convert report.org report.opml$ cv convert report.org report.opmlQuestions.What people ask about ORG to OPML.
Yes. Each heading is one item, and items nest by heading level.
It goes into a first item. That item is named after #+TITLE, or after the file name if there is no title.
Yes. They stay in the headings.
No. They are left out, as in an Emacs export. Drawers, planning lines and source block results are left out too.