TL;DR - If your message already exists in Markdown, do not rebuild it
inside WhatsApp line by line. Keep the structure in Markdown, convert it into
WhatsApp-friendly message text, check the preview and live character count,
and paste. Use depapel for the formatting step. Use WhatsApp for the
final send.
A lot of WhatsApp writing does not start in WhatsApp anymore.
It starts in Markdown.
Maybe ChatGPT, Claude, or another AI assistant gave you a reply in Markdown.
Maybe the message came from internal notes, a changelog, an incident summary, or
support guidance that already has headings, bullets, links, and code fences.
At that point, the hard part is often done. The message exists.
The friction starts when you try to paste that Markdown into WhatsApp without
making it look broken.
The practical workflow
Use this order:
- Write or edit the message in Markdown first.
- Keep the structure tight: short sections, real bullets, and only the
emphasis that helps.
- Convert the Markdown into WhatsApp-friendly message text.
- Check the preview, character count, and any renderer notes before copying.
- Paste the final text into WhatsApp.
- Attach images separately if the message depends on media.
That is the useful split.
Markdown stays the authoring format.
WhatsApp becomes the delivery surface.
Why the default copy-paste path gets messy
The weak version of this workflow looks like this:
- Draft in Markdown.
- Paste raw Markdown into WhatsApp.
- Notice that the message looks wrong.
- Start fixing it by hand.
That usually creates avoidable cleanup work.
Common problems:
**bold** markers do not map cleanly to WhatsApp-ready message text.- Markdown headings become noisy instead of acting like message structure.
- Bullets and task lists lose rhythm or need cleanup by hand.
- Tables are hard to read inside a chat thread.
- Images and raw HTML do not belong in a copied text-only message.
- You waste time stripping syntax that was only there to preserve structure in
the original source.
This is the important mental model: if the structure already exists, the job
is to preserve it, not rewrite it.
The WhatsApp boundary that matters
WhatsApp is a messaging surface, not a full Markdown renderer.
WhatsApp's own
Help Center
supports message formatting such as bold, italic, strikethrough, and
monospace. That is useful, but it is not the same thing as pasting full
Markdown and expecting everything to render as-is.
That means the real job is not "make WhatsApp understand Markdown."
The real job is "turn Markdown structure into message text that still reads
cleanly after paste."
A concrete Markdown example
Markdown source:
# Client handoff for today
Here is the quick status update.
- [x] Docs shipped
- [x] Billing copy approved
- [ ] Mobile fix still under review
## One command worth keeping visible
```bash
pnpm build
```
That source already contains the important parts:
- a strong opening label,
- one short explanation,
- a checklist,
- and a command worth isolating visually.
The WhatsApp version should preserve those signals instead of collapsing them
into one flat paragraph or exposing raw Markdown markers everywhere.
What a good Markdown-to-WhatsApp conversion should keep
If the source is Markdown, the useful conversion is structural first.
It should preserve:
- short section breaks,
- bullets and checklists that still scan well in chat,
- isolated code when it matters,
- emphasis that turns into WhatsApp-friendly markers,
- and a live character count before you copy.
If the source contains tables, images, or raw HTML, the honest behavior is to
simplify them instead of pretending chat text can preserve everything.
Where depapel fits
depapel is the formatting layer for this exact job:
- paste Markdown into the editor,
- switch to the WhatsApp preview,
- review the live character count,
- check any renderer notes if tables, images, or raw HTML were simplified,
- and copy the final message into WhatsApp.
The product role is intentionally narrow.
depapel does not send the message through WhatsApp for you.
It does not pretend chat is a full document surface.
It formats the message so the pasted result stays readable and intentional.
That is the useful part when the writing already happened somewhere else.
When to use something else
Use WhatsApp directly instead if:
- you are writing a short message from scratch,
- you only need one bold or italic phrase,
- or the source is already plain text.
Use a document export instead if:
- the content is really a handoff doc, not a chat message,
- the content depends on images or layout,
- or the source includes important tables that should stay table-shaped in
PDF or DOCX.
Use depapel when:
- the source already exists in Markdown,
- you want a cleaner WhatsApp paste without hand cleanup,
- you want a preview plus a live character count before sending,
- or the message came from AI, notes, docs, or a README that already has
structure.
Honest limitations
This workflow still has limits.
- depapel does not send to WhatsApp for you.
- Images are reduced to alt text or URLs because the copied output is text-only.
- Tables are converted into monospace plain text for easier chat readability.
- Raw HTML is stripped because chat copy should stay plain text.
- You should still do one paste check in WhatsApp before sending if spacing is
especially important.
That is fine.
The value is not turning WhatsApp into a full Markdown renderer.
The value is keeping your source structure intact long enough to produce a clean
message.
Final rule to remember
If the source already exists in Markdown, do not retype the message inside
WhatsApp.
Keep the writing in Markdown.
Convert the structure into WhatsApp-friendly message text.
Then paste the result.
That is the cleaner workflow: write once in a format that is easy to edit, then
use a formatter for the final message surface instead of turning WhatsApp into a
manual cleanup step.
Reference
Please enable JavaScript to use depapel.