Writing posts
Write in a rich-text editor that supports bold, italic, links, headings, and lists, plus markdown shortcuts — and see each render natively per platform.
You write your post in a rich-text editor that supports bold, italic, links, headings, and bullet or numbered lists. Because no two networks offer the same formatting, Inklate renders each of those the platform-native way when it adapts your story for a channel.
The editor and its formatting
The editor is a pinned subset of formatting — the parts that survive across social platforms. Select text to raise a small toolbar with bold, italic, and link. On the Base tab you also get headings (H1–H3) and bullet and numbered lists; per-channel tabs keep the inline set (bold, italic, links) since their text fields have no place for block structure.
The subset is deliberate: the editor can only produce what the content contract accepts, so nothing you type can become a shape a platform later rejects.
Markdown shortcuts
You can write markdown-style as you type — **bold**, a # prefix for a heading, - for a bullet — and the editor converts it to formatting inline. Pasting or typing a URL turns it into a link automatically.
Agents and the API get the same convenience: create_post and update_post accept a markdown string for any rich-text field and parse it server-side to the same subset. Markdown is input-only sugar — reads always return the structured content.
How formatting renders per platform
When your story is adapted to a channel, formatting is degraded to whatever that platform actually supports. None of the four live networks render styled rich text in a feed post, so:
| Formatting | X | |||
|---|---|---|---|---|
| Bold / italic | Unicode glyphs | Unicode glyphs | Unicode glyphs | Unicode glyphs |
| Headings | Bold standalone line | Bold standalone line | Bold standalone line | Bold standalone line |
| Lists | • / 1. plain lines | • / 1. plain lines | • / 1. plain lines | • / 1. plain lines |
| Links | Inline | Inline | Plain text | Inline |
In prose: bold and italic become unicode glyph substitutes on LinkedIn, X, Instagram, and Facebook alike, since none support real styling in a post. A heading becomes a bold standalone line, and a bullet or numbered list becomes plain lines prefixed with • or 1. on every platform. Links stay inline on LinkedIn, X, and Facebook, but render as plain text on Instagram, whose captions aren’t clickable.
This degradation happens when a channel adapts from the story. Once a channel is tailored, its copy is stored as-is — see how that divergence is tracked in Per-channel variants.
What counts against the limit
Each channel enforces its own character limit, and the editor’s counter uses the same counting rule that the publish gate does, so the number you see can’t disagree with what ships. Most platforms count by grapheme; X counts every link as a fixed weight regardless of its real length, mirroring its link shortening.
A tour of the composer
The composer is one screen where you write a post once and adapt it per channel — a Base tab, per-channel tabs with native previews, a sync bar, and a rail.
Per-channel variants
One story becomes a separate, independently editable copy per channel. A sync bar tracks whether each still matches the story or has diverged.