md2chat

DingTalk, WeChat, Feishu, WeCom and email compatibility

Compare destination workflows and distinguish implemented clipboard formats, tested drafts and verified sent messages.

Content reviewed：

Choose by destination

Mac DingTalk uses its native rich-text representation; Windows generates a DingTalk node tree with embedded PNG. Desktop Feishu uses editor fragments and requires an expanded rich-text input. WeChat uses standard HTML. WeCom with images uses sequential text and PNG copies. Email preserves editable HTML tables.

What has been tested?

Mac DingTalk text/image/text was tested on Apple Silicon. In Mac WeCom 5.0.12 (70798), five web segments with two images and three desktop segments with one image were pasted into drafts; those tests did not send messages. Mac Feishu has a two-image mixed-text test and user confirmation after sending.

What is still unverified?

New Windows DingTalk and Feishu generation paths require acceptance in their destination clients. Windows Feishu uses an editor sample from version 7.51.0.45 as implementation evidence. Windows WeCom and delivered email images remain unverified. Source samples, system clipboard round trips and successful builds do not establish destination acceptance.

Privacy and editable content

Conversion runs locally without an account. Remote images still contact their original hosts, and native copying may cache PNG files locally. Ordinary text stays editable; tables and code in images do not. WeCom emphasis styling is not guaranteed. Copying does not send messages.

Step by step

  1. Copy Markdown from your source and paste it into md2chat.
  2. Check the text, table image and final paragraph in the preview.
  3. Choose your destination and inspect the result in your own draft.

A public example

# Weekend book club

Start: see you on Saturday.

| Activity | Duration |
| --- | --- |
| Quiet reading | 20 minutes |
| Discussion | 30 minutes |

End: remember to bring a book.

Check the opening text, table image and closing text in your own draft. Ordinary text should remain editable.

Try the sample in the editor

Implementation and validation records

Related guides