Turn a tweet into a blog image
An official tweet embed loads third-party JavaScript, an iframe and webfonts, costing hundreds of kilobytes and a measurable hit to Largest Contentful Paint. Worse, if the post is later deleted the embed collapses and your article has a hole in it.
Paste a link above to see the preview here.
Have a list of tweets? Use the bulk converter to turn them all into a ZIP.
The card keeps the author's name, handle and timestamp so your export credits them. The post itself still belongs to whoever wrote it, so check you have the right to reuse it before you publish.
A static WebP is a few tens of kilobytes, renders instantly, and still shows the tweet if the original disappears. This page opens in WebP at a modest scale, which is the right trade for something inside article text rather than a hero image.
Questions
- Is an image better than an official tweet embed?
- For page speed and durability, yes. Embeds cost third-party JavaScript and break when a post is deleted. Link to the original alongside the image for attribution.
- Why WebP for a blog?
- It is 25-35 percent smaller than PNG or JPG at the same quality, which directly helps Largest Contentful Paint.
- Should I still link to the original tweet?
- Yes. The image is for readability; the link is attribution and lets readers verify it.