md2rich

2026-07-04

Capcat + md2rich 2026: CLI Web Archiver to Rich Text Pipeline

A new open-source tool called Capcat (capcat.org) entered the Markdown ecosystem in mid-2026. It is a CLI/TUI article archiver that fetches a web page and outputs clean Markdown — no browser, no GUI, no account. For anyone who already uses md2rich to convert Markdown to rich text for social and publishing platforms, Capcat closes a gap: getting content into your Markdown pipeline from the open web.

The complete pipeline at a glance:

capcat URL > draft.md edit in your Markdown editor paste into md2rich.com paste rich text to LinkedIn / X / Medium / Substack

Why CLI Archiving Matters in 2026

Most web archiving tools fall into one of two camps: browser extensions (SingleFile, ArchiveBox, MarkDownload) that require you to be in a browser, or hosted services (Pocket, Notion Web Clipper, outline.com) that upload your content to a third party. Both have drawbacks:

Capcat solves all three: it is a single CLI binary, runs locally, and outputs Markdown directly. That means you can curl some-api-docs.io/page and pipe the result into your writing pipeline without ever opening a browser tab.

Installing Capcat

Installation is straightforward on any Unix-like system:

# macOS via Homebrew
brew install capcat

# Linux — download binary
curl -LO https://capcat.org/releases/capcat-linux-x86_64.tar.gz
tar xzf capcat-linux-x86_64.tar.gz
sudo mv capcat /usr/local/bin/

# Or build from source (Rust)
cargo install capcat

After installation, verify with capcat --version. The project documents Linux, macOS, and Windows — this guide covers macOS and Linux.

Step 1: Archive a Web Page as Markdown

Basic usage is a single command:

capcat https://example.com/blog-posts/2026/editor-roundup > archive/editor-roundup.md

This fetches the article, extracts the main content using readability heuristics, and writes clean Markdown to archive/editor-roundup.md. The output includes:

To see what Markdown it produces for a specific page, pipe to stdout first: capcat https://example.com/article | head -50.

Step 2: Edit and Remix the Markdown

Once you have the Markdown file locally, open it in your editor. This is where the real writing happens — Capcat gives you the source material, but your voice and commentary are what turns an archive into content:

  1. Trim the extract — Capcat is conservative and keeps more content than you need. Delete boilerplate, remove sections irrelevant to your angle.
  2. Add your own sections — your analysis, your examples, your screenshots table. The archive is raw material, not a final draft.
  3. Reword and restructure — Capcat preserves the original paragraph flow; you may want to reorder points for your audience.
  4. Add internal links — link to your own previous articles, your product, or related resources.

After editing, save a clean Markdown file ready for the conversion step.

Example: edited Markdown ready for md2rich

# Editor Roundup 2026: Top Tools Compared

Capcat archived a comparison article from a tech blog.
I trimmed the intro, kept the comparison table data,
added my own take on each editor, and linked back to
my previous roundup post.

## Obsidian — the productivity powerhouse
Capcat extracted Obsidian's feature list from the source.
I added my own note about its plugin ecosystem ...

## VS Code — the dark horse
The archive preserved VS Code's Markdown extension list.
I reorganized it by category for readability ...

Step 3: Convert to Rich Text with md2rich

Now that you have a clean, edited Markdown file, open it and copy the content to your clipboard. Head to md2rich.com — the editor is a single-page app with no install, no signup, and no upload:

  1. Paste the Markdown into the left panel of md2rich
  2. Select your target platform — LinkedIn, X Articles, Medium, Notion, Substack, or Bluesky long-form. md2rich adjusts the output to what each platform's editor accepts (headings flatten to bold on LinkedIn, code blocks format as monospace on Medium, tables reflow on Notion, etc.)
  3. Click "Convert" or "Copy" — the rich-text version goes to your clipboard
  4. Paste into the target editor — formatting intact

Because md2rich runs entirely in your browser (no network request for the conversion), your draft and the archived source material never touch a server. The full pipeline — Capcat on the terminal, editing locally, md2rich in the browser — stays 100% offline-capable.

Privacy-first by design

Capcat runs locally (no upload). Md2rich runs in your browser (no upload). Your source articles, your drafts, and your published content never leave your machine until you deliberately paste into a platform's editor. This is the only end-to-end web-to-rich-text pipeline that handles "sensitive until published" content correctly.

Power Use Cases

Beyond the basic workflow, the Capcat + md2rich combination unlocks several power-use patterns for content creators:

Batch Research — Topic Clusters

When researching a topic cluster (e.g. "best Markdown editors 2026"), archive 6-8 comparison articles in one session:

for url in $(cat editor-comparison-urls.txt); do
  capcat "$url" > "research/$(echo $url | md5 | head -c 8).md"
done

Archive all sources in parallel, then open each Markdown file, extract the comparison data, and write your own synthesis article. Convert the final draft with md2rich and publish.

Competitor Monitoring — Weekly Brief

Run a weekly cron script that archives your competitors' blog posts and documentation updates, produces a Markdown summary, and converts it to a LinkedIn newsletter-style post via md2rich. Your research pipeline becomes your content pipeline.

Documentation Repackaging

Archive API docs, changelogs, or release notes from upstream projects. Edit them into a tutorial format tailored to your audience. Convert with md2rich and cross-post to your preferred platforms.

How Capcat Compares to Other Web-to-Markdown Tools

There are several ways to get web content into Markdown. Here is how Capcat stacks up against the alternatives:

Tool Type Output Offline Batch Privacy
Capcat CLI Markdown Yes Yes (pipe) 100% local
MarkDownload Browser ext Markdown Yes No (per-page) Local
Pocket / Notion Clipper Browser ext HTML No No Uploads server
SingleFile Browser ext HTML Yes No Local
pandoc (URL input) CLI Markdown Yes Yes Local

Capcat's differentiator is the focused scope: it extracts articles to Markdown with no configuration, no browser dependency, and the output is designed to be piped directly into a writing workflow. Pandoc can also fetch URLs but requires more setup for readability extraction (you need a custom Lua filter or an external readability wrapper).

FAQ

Can Capcat handle paywalled or JavaScript-heavy pages?

Capcat uses static HTTP fetching, so it cannot render JavaScript. For JS-rendered pages (SPAs, React docs that hydrate content client-side, dynamic paywalls), the output may be incomplete. For those cases, combine Capcat with a headless browser tool like Playwright or Puppeteer that dumps the rendered HTML, then pipe that into Capcat's local file mode.

Does Capcat preserve images and formatting from the original page?

Images are preserved as Markdown image links (alt text in brackets, URL in parentheses). Inline formatting (bold, italic, links) is preserved. Tables are extracted if the source uses proper HTML table markup. Code blocks are preserved with language annotation when detectable. Layout elements (sidebars, navigation, ads, related-content widgets) are stripped by the readability heuristic.

Can I use Capcat with md2rich entirely offline?

Yes, with one qualification: md2rich.com is a web app, so you need a browser and network access to load the page. However, once loaded, the entire conversion runs client-side in your browser (JavaScript). Your Markdown is never sent to a server. Capcat runs entirely offline once installed. So the pipeline is "offline-capable" — you can archive and edit on a plane, then convert when you have a browser with network access to load md2rich.

Does Capcat support batch processing?

Yes. Capcat accepts URLs from stdin and supports --output-dir for batch saves. You can pipe a list of URLs through xargs or a shell loop. The tool includes a rate limiter (configurable delay between requests) to avoid overwhelming source servers.

Is there an alternative to Capcat for Windows users?

Capcat supports Windows via the prebuilt binary or cargo install in WSL. If you prefer a GUI on Windows, MarkDownload (browser extension) is a reasonable alternative that produces Markdown output with a similar readability extraction, though it lacks batch/pipe support.

Verdict

Capcat fills a real gap in the Markdown creator workflow. Before Capcat, getting web content into Markdown required browser extensions (per-page, manual) or hosted services (privacy leak). With Capcat, the terminal handles the capture step and your Markdown editor handles the writing step. The output goes through md2rich for platform-specific rich-text conversion.

The result is a clean, privacy-respecting, end-to-end pipeline: web page → Capcat → Markdown → edit → md2rich → rich text → publish. For anyone who treats Markdown as their primary writing format and wants to publish to multiple platforms without uploading drafts to an intermediary, this is the setup worth building.


Try md2rich

Convert Markdown to rich text for LinkedIn, X Articles, Medium, Notion, Substack, and Bluesky. No upload, no account, no install.

Open md2rich.com