Turning Markdown outlines into LinkedIn carousel cards
Writing a social carousel in plain Markdown lets you focus on structure and clarity before worrying about box alignment. Block elements such as ATX headings, thematic breaks (---), bullet lists, and pipe tables are parsed deterministically according to the CommonMark 0.31.2 Markdown Specification.
Using Auto, — dividers, or H1 and H2 heading splits
Choose Auto (— or H1/H2) under Split slides by to detect --- horizontal rules automatically and fall back to top-level headings when no dividers are present. Switch to — dividers when a single slide needs multiple ## subheadings, or pick H1 / H2 headings for outline-first notes.
You can paste directly into Markdown slides, click Load sample to inspect a 5-slide template, or drop .md, .markdown, and .txt files up to 5 MB. For long-form reports that belong in a standard reading layout instead of social cards, compile long-form notes into a standard paginated document with full page margins.
Customizing themes, author handles, and slide numbers locally
Select a visual palette from Theme and watch the Slide filmstrip update at a 0.28 preview scale as you type. Enter an Author or brand handle to stamp @yourhandle or your domain consistently along the bottom edge of every card.
Keep Show slide numbers and swipe arrow checked so readers see slide progress (1 / 5) and a subtle directional cue on intermediate cards.
The live Slide filmstrip scrolls horizontally so you can spot awkward line wraps or crowded tables before exporting. Editing any heading or bullet updates every affected card immediately without reloading the page.
When should you pick Portrait 4:5 vs Square 1:1 or 16:9 slides?
Pick Portrait 4:5 (1080 by 1350 px) for LinkedIn document carousels and Instagram feeds because taller cards claim more vertical mobile screen space. Choose Square 1:1 (1080 by 1080 px) for cross-platform grids, or Landscape 16:9 (1920 by 1080 px) for desktop embeds and widescreen decks.
Every frame renders at exact pixel dimensions using the MDN Web Docs HTML5 Canvas API before packaging into your chosen output container.
| Option | Dimensions (px) | Output file | Best platform or workflow |
|---|---|---|---|
| Portrait 4:5 | 1080 × 1350 px | LinkedIn PDF | LinkedIn mobile feeds and Instagram |
| Square 1:1 | 1080 × 1080 px | PNG / JPG ZIP | Cross-platform carousels and grids |
| Landscape 16:9 | 1920 × 1080 px | PNG / JPG ZIP | Widescreen embeds and desktop decks |
| LinkedIn PDF | Uniform multi-page | Single .pdf |
LinkedIn document carousel posts |
| PNG / JPG ZIP | Numbered images | .zip archive |
Instagram, Threads, and X posts |
When a slide needs syntax-highlighted programming examples with window chrome rather than prose bullets, generate standalone syntax-highlighted code snippet cards to drop into your post.
How does Markdown slide splitting handle tables and long lists?
The slide planner splits your outline on --- dividers or headings and then auto-paginates overflowing Markdown slides without clipping tables or long lists. Before drawing each canvas, it estimates every block’s height and moves excess rows or list items onto a clean continuation slide.
Estimating block height against padding and footer reserves
Each canvas reserves a 36 px outer margin, 68 px horizontal inner padding, 72 px top padding, and a 104 px footer reserve at a 29 px base font size. Measuring heading multipliers (1.9× for H1, 1.5× for H2) and wrapped line counts keeps margins consistent across every card.
If your carousel explains system architecture or state machines, you can also render architecture flowcharts as crisp PNG or SVG diagrams before assembling your final deck.
Keeping uniform page geometry for LinkedIn document posts
LinkedIn document posts expect identical page sizes throughout the uploaded file, matching the uniform page-box model in the Library of Congress PDF 2.0 (ISO 32000-2) Format Description. Exporting LinkedIn PDF writes every canvas at the exact same aspect dimensions so mobile and desktop viewers never jump or crop between swipes.
Optimizing PNG or JPG ZIP bundles and client-side privacy
Once your slide filmstrip looks balanced, pick the container format that matches your publishing channel. All rendering and compression stay inside local browser memory with 0 bytes uploaded.
Choosing lossless PNG versus smaller JPG archives
Select PNG slides (.zip) for sharp typography, tables, and high-contrast diagrams, or JPG slides (.zip) when platform upload limits favor compact file sizes. Both PNG pixel streams and .zip archive entries use lossless Deflate compression as specified in IETF RFC 1951 DEFLATE Compressed Data Format.
Tip: Keep each Markdown slide to 1 heading and 3 to 5 concise bullets so readers can scan every card on a phone screen without triggering overflow splits.
Keeping draft outlines and .md files inside your browser
Unreleased product roadmaps, internal benchmarks, and draft threads stay strictly in your tab memory until you click Export carousel. If you also need to strip Markdown formatting for plain-text captions, use Markdown to plain text alongside your slide export.
Because the renderer draws each slide onto an isolated HTML5 canvas in memory, no third-party font CDNs or cloud image APIs ever see your text. Closing or refreshing the browser tab clears your draft outline immediately.