← Back to blog

How to Save Confluence Pages as Markdown

· Save Team
confluencedocumentationwikienterprise

Confluence is where corporate knowledge goes to live --- and where it’s nearly impossible to get back out. Atlassian’s proprietary storage format, clunky export, and WYSIWYG editor make extracting clean content painful. Here’s how to save Confluence pages as Markdown.

Why Save Confluence as Markdown?

Getting content out of Confluence is notoriously difficult:

  • Proprietary format --- Confluence stores content in its own XML-based format
  • HTML export is bloated --- full of Atlassian macros, styles, and markup
  • No native Markdown export --- not an option in the export menu
  • Bulk export is chaotic --- space exports produce nested HTML with broken links
  • Vendor lock-in --- migrating away from Confluence is a project in itself

What Save Captures from Confluence

Page Content

  • Full page text with heading hierarchy
  • Tables (properly formatted as Markdown tables)
  • Code blocks with language tags
  • Info panels and notes (converted to block quotes)
  • Expand/collapse sections (expanded content)
  • Bulleted and numbered lists
  • Internal and external links

Example Output

# Deployment Runbook — Production API

**Space:** Engineering
**Last updated:** March 12, 2026

---

## Pre-Deployment Checklist

- [ ] All CI checks passing on main
- [ ] Database migrations reviewed and approved
- [ ] Feature flags configured for gradual rollout
- [ ] On-call engineer identified and available
- [ ] Rollback plan documented

## Deployment Steps

### 1. Create Release Branch

\`\`\`bash
git checkout main && git pull
git checkout -b release/v2.4.1
git push -u origin release/v2.4.1
\`\`\`

### 2. Run Database Migrations

| Environment | Command | Timeout |
|-------------|---------|---------|
| Staging | `npm run migrate:staging` | 5 min |
| Production | `npm run migrate:prod` | 15 min |

> **Warning:** Always run migrations on staging first.
> Production migrations require approval from @devops.

### 3. Deploy to Production

Deploy via CI/CD pipeline. Monitor the following:
- Error rate (should stay below 0.1%)
- P99 latency (should stay below 200ms)
- Database connection pool utilization

Use Cases

Migration Away from Confluence

  • Save pages one at a time as clean Markdown
  • Build your new knowledge base incrementally
  • Migrate to Obsidian, Notion, GitBook, or a docs-as-code system
  • No need for expensive migration tools

Personal Knowledge Extraction

  • Save the pages most relevant to your work
  • Build a portable reference library
  • Keep access to documentation after leaving a company
  • Create offline copies of critical runbooks

Documentation Cleanup

  • Save existing pages, clean up in Markdown, and re-import
  • Use as a starting point for documentation rewrites
  • Compare old and new versions in a diff tool
  • Audit documentation quality across a space
  • Save Confluence pages as Markdown for AI processing
  • Feed internal docs to AI tools for better search
  • Build a Markdown corpus for RAG (Retrieval-Augmented Generation)
  • Get AI-powered answers from your company’s knowledge base

Tips for Best Results

  1. Save from the page view --- not the editor, not the space overview
  2. Expand all sections --- click to expand any collapse/expand macros before saving
  3. Attachments --- Save captures text content; download attachments separately if needed
  4. Macros --- Confluence macros (Jira links, charts) convert to plain text or links
  5. Permissions --- Save can only capture pages you have access to view

Get Started

Install Save from the Chrome Web Store --- free your Confluence content.

Have questions? Reach out at [email protected]