Upload up to 3 sources — PDFs, Word docs, slides, spreadsheets, text files, Google Drive files, or a URL — pick the Markdown Doc tile, and Scholarly generates a .md file with a clear heading hierarchy, short sections, and tables or lists where they fit, saved to your library and ready to download. The Free plan includes one lifetime AI creation and one upload (8MB or 32 PDF pages). Premium ($30/mo or $144/yr) allows 10 AI creations per week and Laureate ($99/mo) allows 80.
Pasting a chat answer into Notion or a wiki is where formatting goes to die: headings flatten, tables become pipes and dashes, and the next person has to rebuild the structure by hand. The Markdown Doc tile writes the structure into the file itself, so it renders the same in every editor that reads Markdown.
Because the generator reads your uploaded sources, the sections follow your material — the steps in your process document, the topics in your lecture, the findings in your papers. Where the source is thin, the section stays short instead of being padded with generic filler.
The result is a real .md file in your Scholarly library, stored next to the source it came from. Download it, commit it, import it, and when the source changes, generate again with the same instructions to refresh the document.
The Markdown tile is deliberately focused on structure. These are the boundaries to plan around.
Teams use the Markdown Doc tile to turn the documents nobody reads into the pages everybody uses: policy PDFs into internal wiki pages, recorded walkthroughs into SOP docs, design decks into READMEs, and vendor manuals into runbooks. Because the output is plain text, it lives in Notion, Confluence, or a Git repository without a conversion step.
Teams plans add shared libraries, so the source documents, the generated Markdown, and the SOPs built from them stay together where the whole team can reach them.