Skip to main content

confluence2md

Export Confluence pages to Markdown files because using Confluence (or any other Atlassian product for that matter, like Jira) sucks. Works as a CLI tool and as a Python library.

Installation

uv sync

Configuration

Copy config.yaml.example to config.yaml and adjust it to your Confluence instance:

confluence:
  url: https://your-instance.atlassian.net/wiki
  token: your-personal-access-token
  username: your-email@example.com

output:
  directory: ./export
  filename_pattern: "{title}"
  include_children: false
  include_labels: true
  include_metadata: true

The token can also be set via the CONFLUENCE2MD_TOKEN environment variable. The username can be set via CONFLUENCE2MD_USERNAME.

For Confluence Cloud, both username (your email) and token (API token) are required. For Confluence Server/Data Center with personal access tokens, only token is needed.

CLI Usage

Export pages matching a CQL query:

confluence2md export --cql "space = DEV AND label = api"

Export a single page by ID:

confluence2md export --page-id 12345

Export a page and its children:

confluence2md export --page-id 12345 --include-children

Export all pages from a space:

confluence2md export --space DEV

Override the output directory:

confluence2md export --cql "space = DEV" --output-dir ./docs

Use a specific config file:

confluence2md -c path/to/config.yaml export --space DEV

List available spaces:

confluence2md list-spaces
confluence2md list-spaces --search "dev"

Library Usage

from confluence2md import load_config, connect, fetch_pages_by_cql, export_pages

config = load_config("config.yaml")
confluence = connect(config.confluence)
pages = fetch_pages_by_cql(confluence, "space = DEV", max_results=100)
paths = export_pages(pages, config.output)

You can also render Markdown without writing files:

from confluence2md import render_page

markdown = render_page(page, config.output)
print(markdown)

Releasing

./scripts/release.sh patch  # 0.1.0 → 0.1.1
./scripts/release.sh minor  # 0.1.0 → 0.2.0
./scripts/release.sh major  # 0.1.0 → 1.0.0

This bumps the version in pyproject.toml, commits, tags, and pushes. The push triggers a GitHub Actions workflow that publishes the package to PyPI.

License

MIT

Release files for confluence2md 0.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for confluence2md 0.3.0
File Size Uploaded
confluence2md-0.3.0.tar.gz 44.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for confluence2md 0.3.0
File Interpreter ABI Platform
confluence2md-0.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 55.2 kB

Release files / confluence2md-0.3.0.tar.gz

Download URL confluence2md-0.3.0.tar.gz
Size 44.7 kB
Tags Source
SHA-256 checksum
How to use checksums
af0151feb5a24bb5564384dd1b90d75e6fbbde3366f71835d4f91715696e434a
BLAKE2b-256 checksum
How to use checksums
58766083ee516847dbf75b1d8481a0917626bafbb7846968131f42daa176d847
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 27, 2026.

Transparency log

Release files / confluence2md-0.3.0-py3-none-any.whl

Download URL confluence2md-0.3.0-py3-none-any.whl
Size 10.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
10217eac1b16759b42d4418fff72c7bee734d7874435eea53b3df893ff40c58c
BLAKE2b-256 checksum
How to use checksums
a58362e6d6b766067e26154d7433d96a8f3edb20b79a3ed206bca7182f5fbde7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Mar 27, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.3.0 This release

2 release files

0.2.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page