High-Resolution Tweet Screenshots for Publishers and Journalists

Web article: 2× density (~1200 pixels wide for a standard tweet) is enough for a full-width blog embed. Anything less looks fuzzy on retina displays; anything more just bloats page load without visible benefit.

Print / magazine: 300 dpi is the print industry standard. For a 4-inch-wide print embed, you need 1200 pixels minimum — the tool's 2× output covers it. For a full-page print at 8 inches wide, use the tool's 3× density option if available, or scale up carefully in a rasterizer that handles font-hint upscaling.

Academic paper / court filing: 300 dpi PNG plus a provenance appendix (Wayback URL, capture date, SHA-256 hash).

1. Copy the tweet URL. 2. Immediately submit it to the Wayback Machine at web.archive.org/save — this creates a public, timestamped record of what X was serving at that moment. 3. Open /twitter-screenshot-downloader, paste, download the PNG at 2× (web) or 3× (print).

4. Compute the SHA-256 hash: shasum -a 256 tweet.png. 5. Store the URL, Wayback link, hash, and PNG together in the article's assets folder. This bundle is what a fact-checker or lawyer will ask for later.

Every embedded screenshot must credit the original author. Best practice: caption the image with "@handle on X, {date}" and include a link to the original post in the caption where possible. If the post has since been deleted, note "post deleted on {date}" and reference the Wayback URL.

Some outlets go further and DM the author before publishing embedded screenshots. This is not legally required for public tweets, but it's a courtesy that avoids after-the-fact takedown requests and often surfaces useful additional context.

Deleted tweets are one of the most powerful uses of this workflow. If the tweet gets deleted after you download, your PNG plus the Wayback capture plus the hash forms a complete evidentiary bundle. This is how newsrooms in 2024–2026 preserved dozens of consequential tweets that were later deleted.

Edited tweets (X's edit feature, launched 2022 for Premium subscribers) present a subtler issue. Only Premium accounts can edit and only within 60 minutes of posting. Your capture might reflect a pre-edit or post-edit state. Note the exact time of capture in your provenance metadata; the tool doesn't currently pull the edit history from X.

Screenshots of public tweets are broadly protected in US journalism under fair use and the First Amendment when used for reporting, commentary, or criticism. Non-US jurisdictions vary. In the EU, GDPR and the Right to be Forgotten intersect with journalism carve-outs — get local legal advice for high-stakes stories.

Regardless of jurisdiction, the safe pattern is: use only the tweet content necessary for the story, credit the author, link back to the original when possible, and preserve provenance so any challenge can be met with evidence. The US Copyright Office fair use index is a starting point for American publishers.

For long-term archival (multi-year retention), store the PNG in a cold-storage tier (S3 Glacier, Backblaze B2, Wasabi) plus at least one warm mirror. Keep the hash separate from the file — same-drive storage of file and hash doesn't prove tampering resistance because both can be edited together.

For hyper-important captures (breaking political news, whistleblower content), also upload to the Internet Archive as a public or private collection. Third-party custody adds an independent witness that the file existed at a specific date.