How to Publish from Obsidian to a WeChat Public Account

The question "How do I publish from Obsidian to a WeChat public account?" looks simple on the surface. In practice, it is not just about export format.

It also includes:

• keeping Obsidian as the writing environment
• getting content into WeChat-ready formatting
• deciding whether later steps should stay manual or become automated

If you only ask whether Obsidian can export Markdown, you are not looking at the full workflow.

Why so many people want this path

Obsidian is already a strong environment for long-term writing:

• it works well with Markdown
• notes and source material stay in one place
• ideas, drafts, and references can live together
• it suits individual creators and small teams

The friction starts after writing. The WeChat backend is not built around Markdown, so an adaptation layer is unavoidable.

The common path that works, but does not scale well

Many people still use this sequence:

1. Write in Obsidian
2. Copy into a web formatter
3. adjust styles and images
4. paste it into the WeChat backend

It works, but the weaknesses are obvious:

• too many steps
• a long copy chain
• repetitive work for frequent publishing
• poor fit for later automation

A smoother path: plugin first, API later

For most Obsidian users, the more realistic order is:

1. Keep Obsidian as the writing base
2. Use a plugin for WeChat formatting and preview
3. Add APIs or workflow automation only after the basic path is stable

obsidian-md2wechat fits that first step. It handles the segment between Obsidian and WeChat formatting.

Why a plugin is the better first step

Because it solves the most immediate problems:

• you stay in Obsidian
• you can inspect the formatting result quickly
• you can switch themes
• you can prove the output before redesigning the whole publish process

Only after that is stable does it make sense to evaluate:

• the Convert API
• the article draft API
• the newspic draft API
• media upload

The three layers to separate clearly

This workflow gets much easier if you split it into three layers.

1. Writing entrypoint

Is Obsidian where the content is created?

2. Formatting

How does Markdown become WeChat-ready HTML?

3. Publish workflow

Do you stop at copy-paste, or continue into draft creation, media handling, and automation?

Once those layers are separated, the product choices become clearer.

When to move beyond the plugin

If any of these are true, you are no longer only asking how to publish from Obsidian:

• you publish on a regular schedule
• AI already helps generate or revise content
• you want to reduce manual backend work
• you want a workflow to create drafts, not just formatted HTML

At that point, continue with:

• What Is the WeChat Draft API, and How Is It Different from Markdown-to-HTML Conversion?
• md2wechat-lite: A CLI for Scripts and Agent Workflows
• md2wechat-skill: Bring WeChat Formatting into Claude Code and OpenClaw

Closing thought

The practical route from Obsidian to WeChat is usually not "publish directly from notes." It is:

• keep writing in Obsidian
• stabilize formatting first
• then decide whether the next step should be a draft API or a wider automated workflow

That sequence preserves the writing habit while making the publish chain easier to standardize.