Tweet code snippets that people actually read
The X algorithm downranks posts that send people off-platform. A code screenshot keeps engagement on your tweet — likes, replies, and reposts all stay in the loop.
Why images beat gists and links
External links reduce reach, and GitHub gists render inconsistently on mobile. A styled image renders identically for every follower, on every device.
The 1200×675 preset
X timelines display 16:9 media at up to 1200 pixels wide. The built-in X Post preset outputs exactly that, at 2× retina sharpness, so nothing gets cropped or blurred.
Thread-friendly workflow
Paste a function, screenshot it, then edit the last few lines and screenshot again. Local autosave keeps your snippet between shots so threads stay visually consistent.
How to turn code into a polished image
ClawRecall runs entirely in your browser, so nothing to install and no account needed. TypeScript, JavaScript, Python, Go, Rust, SQL, JSON, and more are all syntax-highlighted automatically.
- Paste or type your snippet into the editor.
- Pick a theme — every palette has hand-tuned syntax colors.
- Choose a preset size built for X, LinkedIn, Instagram, or blog headers.
- Export a retina-sharp PNG or scalable SVG, or copy it straight to your clipboard.
Frequently asked questions
What size should a code image be for X?
1200×675 (16:9) fills the timeline card without cropping. ClawRecall's X Post preset exports exactly this size at 2× retina resolution.
Do code screenshots get more engagement than text?
Visual posts stop the scroll. Styled code images also survive quote-tweets and embeds intact, while pasted text gets reformatted.
Will X compress my image into blur?
X re-compresses uploads, but starting from a crisp 2400×1350 retina PNG means artifacts stay invisible at feed size.
Related tools
Ready to try it?
Open the editor, paste your code, and export a polished image — free, no signup.
Open the editor