How to export highlights to Markdown without making a mess
Exporting highlights to Markdown sounds simple.
In practice, many exports are hard to use.
They include too little context, too much clutter, broken formatting, or no clear connection back to the original source.
A good Markdown export should make future work easier.
What a useful Markdown export should contain
At minimum, a source note should include:
- title
- original URL
- author or source when available
- saved date
- reading time or content type
- highlights
- personal notes
- tags or collections
The highlight alone is rarely enough. You need context.
If a note only says “This is important,” future you will not know why.
The problem with raw clipping
Raw clipped pages often create messy notes.
They may include:
- navigation text
- cookie banners
- duplicated headings
- broken images
- unrelated sidebar content
- weird formatting
That is why the reading step matters.
Save first. Read second. Highlight third. Export last.
The export should be the result of judgment, not the result of a scraper.
A better structure
A practical Markdown export might look like this:
- frontmatter or metadata at the top
- a short source summary
- highlights grouped in order
- notes attached to the right quote
- source URL preserved
- related collections or tags included
This works well for Obsidian, Notion, Logseq, static docs, research folders, and personal writing systems.
Why Sigilla treats export as a workflow step
Sigilla is built around the idea that saved reading should become reusable material.
That means export is not an emergency escape hatch. It is one of the main outcomes.
You save a source, highlight what matters, and then export the useful parts when they are ready.
If you care about Markdown output, start with the dedicated workflow: Obsidian web clipper workflow.