Convert Logseq pages to PDF, Word or HTML
Outline structure and page references handled, so an exported page reads as a document rather than a pile of brackets.
Convert Markdown to PDF
Markdown source
An outliner writing Markdown files
Logseq is an outliner first: every line is a block, and blocks nest. It stores those blocks as Markdown files in a pages folder, so what lands on disk is a bulleted list — often deeply nested — rather than the mix of paragraphs and headings a Markdown document usually contains.
That matters when converting, because a document made entirely of bullets reads differently from prose. Nesting is preserved exactly, so the structure you built survives, but a page that was written as an outline will still look like an outline in the PDF. If you want flowing prose, edit after converting rather than expecting the converter to guess.
Logseq shares Obsidian's page-reference syntax, and it gets the same treatment: [[Another Page]] becomes its display text rather than literal brackets, because a reference into your graph means nothing in an exported document. Block references written as ((uuid)) are identifiers rather than content, so they carry through as written — there is no text to substitute, since the referenced block lives elsewhere in your graph.
Block properties, the key:: value lines Logseq uses for metadata, also come through as written. They are part of the file rather than an artefact of the converter, and are usually worth deleting before you export if the document is going to someone outside your graph.
How to convert a Logseq page
Find the file
Your graph is a folder; pages live in the pages subfolder as .md files. Drop one onto the converter.
Or copy the page
Select the blocks in Logseq and copy — you get Markdown on the clipboard, which you can paste above.
Convert
Choose PDF, Word, HTML or plain text and download.
Every format, from the same file
Logseq to PDF
Produces a paginated PDF with real, selectable text rather than a screenshot of a preview. Headings are never orphaned at the foot of a page and long tables repeat their header row across breaks.
Logseq to Word
Produces a .docx using native Word heading styles, so the navigation pane and automatic tables of contents work and a colleague can edit or comment on it normally.
Logseq to HTML
Produces one self-contained HTML file with the stylesheet inlined — no external assets to host, so it opens correctly from a USB stick or an email attachment.
Logseq to plain text
Lays the note out for a fixed-width reader: underlined headings, tables as aligned columns, prose wrapped at 80 columns. Useful for pasting into a ticket or an email.
Logseq to PDF, Logseq export to PDF, Logseq page to PDF
Logseq's own print-to-PDF captures the page as it appears on screen, bullets and all. Converting the underlying Markdown gives you a properly typeset document instead, and covers Word and HTML, which Logseq does not export at all.
Questions
Will my outline structure survive?
Yes, exactly as nested. Because Logseq stores everything as bullets, the converted document is a nested list rather than prose — that is the file, not the converter.
What happens to page references?
[[Another Page]] becomes its display text. A reference into your graph would point nowhere in an exported PDF, so the words are what carry over.
Do block references resolve?
No. ((uuid)) is an identifier pointing at a block elsewhere in your graph, and the exported text does not contain that block, so there is nothing to substitute.
How do I get rid of the property lines?
Delete the key:: value lines before converting. They are part of the Markdown file itself, so the converter passes them through faithfully.
Is my graph uploaded?
No. Everything runs in your browser — relevant here, since a Logseq graph is usually personal.