Paste code, pick a theme and a background, and download a PNG worth putting in a post or a slide. It renders at twice the display size, so the text stays sharp on the high-density screen almost everyone reads on — a 1x capture looks soft immediately. Choosing no background gives a transparent PNG, so the image sits on a dark or light page without the white rectangle that gives most code screenshots away. There is no syntax highlighting, on purpose: doing it properly needs a parser for every language, and a highlighter that guesses wrong colours a variable as a keyword, which reads as an error in your code rather than in the tool. Indentation is preserved exactly, which for Python or YAML is the whole point.
| Background | Best for |
|---|---|
| Gradient | Social posts — fills the frame |
| Transparent | Slides and docs where the page colour shows through |
| Large padding | Images that will be cropped to a square |
| No padding | Embedding directly in a layout |
Because doing it correctly means parsing each language, and a highlighter that guesses the language wrong is worse than none — a variable coloured as a keyword looks like a bug in your code, not in the tool. For the short snippets people turn into images, plain monospaced text reads fine.
No. The image is rendered in your browser and never leaves it.
It is rendered at twice the on-screen size. Capturing at 1x produces an image that is visibly soft on any high-density display, which is essentially every phone and most laptops made in the last decade.
Yes — choose the last background option. The PNG keeps its transparency, so the card sits on whatever colour your post uses instead of carrying a white box around it.
Exactly as you typed it, including tabs and trailing structure. That matters for Python and YAML, where collapsed whitespace would make the snippet wrong rather than just ugly.
It follows your content and padding, at 2x. A short snippet produces a small image; a long one produces a tall one. Reduce the font size or padding if you need it smaller.
The card is laid out as ordinary HTML and rasterised with html2canvas at twice its display size, because a PNG captured at 1x is visibly soft the moment it is viewed on any modern display — every phone and most laptops have been beyond 1x for a decade. The background is captured as transparent when no gradient is chosen, so the image can sit on a dark or light post without a white rectangle around it, which is the usual giveaway. Syntax highlighting is deliberately absent: doing it properly needs a parser per language, and a highlighter that guesses the language wrong produces colouring that is actively misleading — a variable coloured as a keyword reads as a mistake in the code rather than in the tool. Plain monospaced text is honest and, for the short snippets these images are usually made from, not much worse to read. Whitespace is preserved exactly rather than collapsed, so indentation survives, which for Python or YAML is the difference between a usable image and a wrong one. The filename in the window bar is sanitised before being used as the download name, since a snippet's title routinely contains slashes and colons that no filesystem accepts.