Export a draft as Markdown

1. Open the document in the editor.
2. Open Export in the sidebar and choose Markdown.
3. Pick a folder and a filename in the save dialog. The file is written straight there.

There is no upload in that sequence and no conversion service in the middle: the browser turns the document into text and writes it to the file you picked.

The save dialog uses the File System Access API, which today means Chromium browsers — Chrome, Edge, Brave, Opera. In Firefox or Safari the option explains that and does nothing else; it does not fall back to a download or to a server.

That is the honest trade-off. A browser that cannot write to a chosen path cannot be given a fake one without sending the text somewhere, and sending it somewhere is the thing this app does not do.

• A static site. Hugo, Astro, Eleventy, Jekyll and Next all read Markdown; drop the file into the content folder.
• A notes app. Obsidian, Logseq and friends import plain Markdown without conversion.
• Git. Markdown diffs line by line, which is why documentation lives in it.
• An archive. A .md file opens in twenty years with a text editor and nothing else.

• It is not a Markdown editor. You write rich text; Markdown is the export. That is the point — no ## in the middle of a sentence.
• Images become references, not files. The export writes image links into the Markdown. If a target needs the image files beside the document, export a .quorly package as well.
• No front matter. There is no YAML header to configure; add it in your static site if you need it.

The import side is just as plain: .md, .txt, .docx and .quorly files open in the editor, so an existing plain-text project can come in, be edited, and go back out as Markdown. If you are moving a Google Doc across, the Google Docs to Markdown guide compares the three routes; if you just want to see the Markdown rendered, the preview tool does it without an upload.