MarkCard Studio Turns a Markdown File Into a Social Card in One Export

Open a markdown file with a few headers and a bullet list in MarkCard Studio, pick a theme and a canvas preset, and it comes back as a set of numbered PNGs sized for the platform you named, in under a minute, with no upload and no account. That is the entire pitch of MarkCard Studio, a free, open-source desktop app for people who already write in plain text and want a fast way to turn markdown into social media cards without opening a full design tool for every post.

It is a small project, 278 stars and 13 forks as of this week, built by a single GitHub developer (pangxiaobin) and first created on August 4, 2026. What makes it worth a look is not the traction, it is the fit: MarkCard Studio does exactly one job, markdown in, formatted card images out, and does it entirely on your machine.

What using MarkCard Studio looks like

The app is built on Tauri 2 with a Rust backend and a Vue 3 frontend, and ships as native installers for Windows, macOS (both Intel and Apple Silicon), and Linux (AppImage, deb, and rpm), so getting started does not require cloning a repo or running a build toolchain, six tagged releases have shipped since mid-August, the most recent on August 29. You open or paste a markdown document into a built-in CodeMirror editor, and the app splits it into pages using one of several pagination strategies, by heading, by a target character count, or by manual page breaks you insert yourself. Each page previews live against whichever of the 16 built-in themes you have selected, styles that range from a clean Swiss-grid layout to darker, more graphic looks, and you can switch a canvas preset to match the platform you are posting to: a 3:4 ratio sized for Xiaohongshu, a 9:16 ratio for Douyin, and layouts tuned for Weibo, alongside custom dimensions if none of the presets fit. When the pages look right, you export as PNG, JPG, a single long PNG for a scrolling format, or a paginated PDF.

The markdown support goes beyond plain text. Tables render as tables, code blocks get syntax highlighting through Highlight.js, and the editor understands KaTeX for math notation and Mermaid for diagrams, so a card can carry a rendered chart or equation without you dropping in a screenshot. Everything is saved locally, with draft recovery if the app closes mid-edit, and the interface itself ships bilingual in English and Simplified Chinese.

How MarkCard Studio actually does the pagination and theming

The mechanic worth understanding before you rely on this for a real posting workflow is the pagination engine, since it is the piece doing the most work. Rather than treating your markdown as one long canvas to be sliced at fixed intervals, it reads structure, headings, paragraph breaks, list boundaries, and tries to keep a logical unit intact on one card rather than splitting a bullet list or a code block across two images. You still get a manual override for any card where the automatic split guesses wrong, which in practice is the difference between a tool you can trust for a ten-card thread and one you have to babysit card by card.

Themes are not just color palettes. Each one carries its own type scale, spacing rules, and treatment for code blocks and tables, so switching themes can meaningfully change how much content fits per card, not just how it looks. That matters if you are optimizing for a specific slide count or trying to match a locked visual system, since a theme swap can silently shift your pagination.

Who this fits and who should skip it

MarkCard Studio is a good fit for a solo creator or a small team that already writes quote posts, breakdown threads, or text-first carousels by hand and wants to cut the manual design pass out of that specific workflow, exactly the kind of quote-and-text card production most accounts do slide by slide in a general design tool. It is local-first by design, so there is no cloud sync, no shared workspace, and no way for a teammate to pick up a draft from another machine, which makes it a poor fit for a team that needs shared brand assets or simultaneous editing.

It is also still pre-1.0 software, versioned at 0.1.5, with a description that flags active development and likely interface changes before a stable release. There is no built-in image library, so a card with a photo behind the text still means dragging that asset in yourself, and the theme set, while varied, is fixed: you are choosing among 16 designed looks rather than building a custom brand system from scratch. If your workflow already lives inside Figma, Canva, or a brand kit with strict layout rules, this will feel more like a fast utility for drafts than a replacement for that system. For anyone whose actual bottleneck is turning a paragraph of notes into a clean, on-brand card without opening a design tool at all, it is a genuinely useful free download.

Source: MarkCard Studio on GitHub.