Feed X Articles to Claude: Step-by-Step Guide

Updated March 2026 · 6 min read

You find a great thread or article on X, think "Claude should see this," and paste the URL into your chat. Claude responds with something like "I can't access that link" or "I'm not able to browse X."

It's frustrating. You know Claude is smart enough to analyze it. But X actively blocks server-side access, and Claude's web browsing doesn't work there. So what now?

The answer: convert the article to Markdown first using xtomd.com, then paste it into Claude. It takes 60 seconds and opens up everything Claude can do — summarize, critique, extract, compare, generate responses.

Here's how to do it.

How do you convert an X article to Markdown?

1. Copy the X article URL — Open the article or thread on X. Click the share button and copy the URL from your browser's address bar. You need the full link — something like https://x.com/username/status/1234567890.
2. Go to xtomd.com — Open xtomd.com in a new tab. You'll see a simple form with one text field.
3. Paste the URL into xtomd.com — Drop the X link into the input field. The tool detects it automatically and starts processing.
4. Copy the Markdown output — Within seconds, xtomd.com generates clean, readable Markdown. Hit the copy button (or select all and copy manually). You now have the article in a format Claude can work with.

That's it. Four steps, less than a minute.

What exactly are you pasting into Claude?

When xtomd.com converts an X article, you get structured Markdown that includes the full text of each tweet in the thread, author info, timestamps, and engagement metrics. No broken links, no media placeholders, no formatting loss. Claude sees readable, structured text.

Five example prompts to use once you have the Markdown

Summarize the main argument:
"Summarize this X thread in two sentences. What's the core claim?"

Critique the logic:
"What's the strongest and weakest point in this thread? Are there gaps in the reasoning?"

Extract actionable takeaways:
"List three things I can actually implement based on this thread. Be specific."

Compare multiple articles:
Paste two Markdown conversions and ask: "These two threads disagree on X. Where do they overlap? What's genuinely different?"

Generate response content:
"I want to quote-tweet this thread with a counterpoint about Y. Draft three versions of a reply — one thoughtful, one provocative, one conversational."

You can also ask Claude to rewrite the thread for LinkedIn, extract the sources cited, explain technical jargon, or build on the ideas with new examples.

Why Markdown works better than screenshots or raw text

Screenshots are static. Claude can read them, but you lose searchability. If you want to edit, share, or version-control it, you're stuck with an image.

Raw pasted text is messy. If you manually copy-paste individual tweets from X into Claude, the structure falls apart. You lose metadata. Threading becomes unclear. Claude has to guess at context.

Markdown is clean and portable. It preserves structure, is easy to edit, works everywhere (Claude, Obsidian, Notion, GitHub), and is human-readable. You can also store it for later.

xtomd.com does the conversion work so you don't have to.

Works with Claude.ai, Claude Code, and Claude API

Claude.ai (free and Pro): Paste the Markdown directly into the chat. Works exactly as described above.

Claude Code: If you're using Claude Code via terminal, save the Markdown to a file and reference it in your prompt. Claude Code can read local files and process them the same way.

Claude API: Developers can integrate xtomd.com conversions into workflows. Convert the article, then send the Markdown to the Claude API in your request. This is useful for building tools that analyze X content at scale.

The workflow is identical across all platforms. Convert first, paste second, analyze third.

The workflow in practice

Here's what this looks like end-to-end:

1. You're scrolling X and find a thread about AI agent architecture.
2. You copy the link and go to xtomd.com. Paste, convert, copy Markdown.
3. You open Claude and paste the Markdown.
4. You ask: "What's the main technical insight here? How does it compare to the ReAct pattern?"
5. Claude analyzes it, gives you a detailed breakdown, and you build from there.

Without the Markdown conversion, you'd be stuck explaining the thread to Claude from memory. With it, Claude has the exact text and can do the heavy lifting.