01
Paste the outline
Drop copied Tana nodes or plain-text exports into the input area. Tabs and two-space indentation are both supported for hierarchy.
Tana export cleanup
Paste copied Tana nodes or plain-text exports, then turn the outline into Markdown headings, nested bullets, and readable field lines.
What you get
Converter
Use tabs or two-space indentation to preserve hierarchy. Fields such as `Name:: Value` will become readable Markdown field lines.
Markdown preview will appear here.
Why this page exists
People looking for Tana to Markdown usually want to preserve thought structure while escaping a tool-specific format. The hard part is not the raw text. It is keeping indentation, field syntax, and nested meaning readable after export.
This page focuses on that translation layer. It turns Tana-style nodes into Markdown you can keep in a repository, a docs folder, or a notes app that does not understand Tana syntax.
How it works
01
Drop copied Tana nodes or plain-text exports into the input area. Tabs and two-space indentation are both supported for hierarchy.
02
The converter promotes the top level into headings, nests child nodes as bullet lists, and rewrites field syntax into readable Markdown lines.
03
Copy the Markdown result or download it for use in Obsidian, GitHub, static docs, or long-term archives.
Best for
Move selected Tana content into a Markdown-first system without losing nested context.
Turn structured Tana weekly reviews and status notes into readable Markdown summaries for teams.
Keep a plain-text backup of important outline content in a format that is easy to search and diff.
FAQ
Yes. It accepts copied Tana-style outline text with tabs or two-space indentation and converts the hierarchy into Markdown headings and nested bullet lists.
Field lines such as `Status:: Draft` are rewritten into readable Markdown field text so the meaning survives after export.
It is useful for people moving notes from Tana into GitHub, Obsidian, plain Markdown archives, docs, or content workflows that need portable text.
Continue with
People rarely stop at one conversion. These adjacent pages pick up the next task in the same workflow.
Open the workspace when you want to reorganize or polish the converted outline.
Use this adjacent route when the source comes from formatted documents instead of Tana nodes.
Switch here for table-shaped source material that should become Markdown rows and columns.
Move into broader normalization and export flows after the outline has been converted.