Markdown to AsciiDoc

It is pandoc's asciidoc writer, not its asciidoctor one. The two differ in the extra syntax Asciidoctor adds, so if your toolchain is Asciidoctor you might want to adjust a few constructs by hand after converting. Plain document structure, headings, lists, links, tables and code blocks, is the same for both.

Because your Markdown had no such thing to convert. Admonitions are an AsciiDoc feature with no Markdown counterpart, so pandoc has nothing to map onto them and will not guess. Add them after converting, or write them in the AsciiDoc file directly from then on.

Image links become AsciiDoc image macros carrying the same path or URL your Markdown used. The image data itself is never read, since the tool hands pandoc only the text of your document. Keep the picture files at the paths the macros name and your AsciiDoc processor will find them.

The .adoc extension, so notes.md becomes notes.adoc. If your build expects .asciidoc or .txt, rename the file after downloading; the content is identical either way. The converted AsciiDoc is shown on the page as well as offered as a download, and the copy button copies all of it even when the on-screen preview is shortened, which helps when you are pasting into a documentation system rather than saving a file. Nothing is uploaded at any point.

Yes, with AsciiDoc to Markdown. That direction is worth knowing about because pandoc historically shipped an AsciiDoc writer and no reader at all; the build here has both, which is why the reverse tool exists. Both directions run entirely in this browser tab.