Documenting a Smear Campaign: Screenshots & Archives

This guide shows you how to create a reliable, timestamped record of an online smear campaign using screenshots and web archives. You will learn what to capture, how to preserve it so it cannot be silently altered or deleted, and how to organize the evidence for your own reference or for reporting to a platform, employer, or attorney.

What You’ll Need

A computer or phone with a web browser (Chrome, Firefox, Safari, or Edge).
A free account at a web archiving service like the Wayback Machine (web.archive.org) or archive.today (archive.ph).
A folder on your device or cloud drive to store the screenshots and notes.
A simple text editor (Notepad, TextEdit) or note-taking app for logging dates and URLs.

Step-by-Step

Create a master log. Open a blank document and create a table with columns: Date/Time (UTC), Platform, URL, Author/Account, Content Summary, and Screenshot File Name. Fill this in as you go. Use UTC (Coordinated Universal Time) to avoid timezone disputes later.
Capture the full context first. Before taking any screenshot, scroll to the top of the page and note the exact URL in the address bar. If the post is part of a thread, capture the thread’s main page first, then the individual post. This establishes where the content lives.
Take a full-page screenshot. On a desktop browser, use the built-in full-page capture feature (e.g., Chrome’s “Capture full size screenshot” in DevTools, or Firefox’s “Take a Screenshot” > “Save full page”). On a phone, take multiple overlapping screenshots and stitch them later if needed. Ensure the date and time are visible on your device’s status bar if possible.
Zoom in on key elements. Take a second screenshot zoomed in on the offensive text, the username, the timestamp (e.g., “3h” or “June 12, 2025”), and any profile badges. This makes the details legible and hard to dispute.
Capture the profile and metadata. Screenshot the author’s profile page, including their handle, join date, follower count, and any bio. Also capture the post’s engagement metrics (likes, shares, comments) if they are part of the smear (e.g., a viral post).
Save the original HTML file. In your browser, press Ctrl+S (or Cmd+S on Mac) and choose “Webpage, HTML Only” to save the raw page source. This preserves the underlying code and metadata that a screenshot misses. Rename the file with the date and platform (e.g., 2025-06-12_twitter_post1.html).
Archive the URL immediately. Go to web.archive.org, paste the exact URL into the “Save Page Now” box, and click the button. Wait for it to finish. Copy the new archive URL (e.g., web.archive.org/web/20250612/https://...) and add it to your master log. If the page is private or behind a login, the Wayback Machine may fail; use archive.today instead, which sometimes handles dynamic pages better.
Verify the archive. Open the archived link in a new incognito/private window. Confirm the content matches your screenshot. If the archive shows a login wall or a blank page, try again later or use a different archiver. Note in your log which archive worked.
Repeat for every new post or edit. Smear campaigns often evolve. Check the original URLs daily and re-archive them. If the original post is deleted, the archived version remains your evidence.
Organize and back up. Create a folder per platform or per incident. Name each file with the date, platform, and a short descriptor (e.g., 2025-06-12_fb_false_accusation.png). Upload the entire folder to two separate cloud drives (e.g., Google Drive and Dropbox) or to an external hard drive.
Export your master log. When done, export your log as a PDF and include it in the evidence folder. This log is your index; it ties every screenshot and archive to a timeline.

Common Mistakes

Only taking screenshots of the visible screen. This misses the URL bar and the timestamp. Always capture the full page and the address bar.
Relying on screenshots alone. Screenshots can be edited. The archived HTML and the Wayback Machine record are far stronger evidence because they are independently verifiable.
Ignoring the URL. Screenshots without the URL in the frame are nearly useless. Always ensure the full URL is visible in at least one image.
Waiting to archive. If you wait a day, the post may be deleted or the account may be suspended. Archive immediately, even if you plan to take better screenshots later.
Not recording the timezone. A timestamp like “12:00 PM” means nothing without a timezone. Use UTC in your log and note the local timezone in the screenshot if visible.

Tips

Use a dedicated browser profile. Create a separate browser profile just for evidence collection. This prevents your personal cookies from changing what you see and keeps the evidence clean.
Enable the browser’s built-in reader mode. If the page has heavy ads or pop-ups, use Reader Mode (the book icon in the address bar) before taking a screenshot. It strips out clutter and makes the text the focus.
Take screenshots of the “view source” of the post. On many platforms, right-clicking the timestamp and selecting “Inspect” shows the exact server time in the HTML. Screenshot that too.
Archive the search results. If the smear appears in search engines, archive the search results page as well. This shows the reach of the campaign.
Keep a separate list of deleted content. If you see a post disappear, note the time you noticed it was gone and add it to your log. This is itself evidence of intent to hide.

Troubleshooting

The page requires a login (Facebook, private Instagram). The Wayback Machine cannot archive these. Use archive.today, which sometimes works with logged-out public views. If that fails, take a full-page screenshot with your logged-in session, but be aware it is less verifiable. Also try Google’s cache: search for the exact URL and click the three-dot menu next to the result, then “Cached.”

The page is a single-page app that loads content dynamically. The archive may capture a blank shell. Wait 10–15 seconds after the page loads before archiving. Use the “Save Page Now” feature in the Wayback Machine, which runs a headless browser that waits for JavaScript. If it still fails, take a screen recording (e.g., on Windows, Win+Shift+R; on Mac, Cmd+Shift+5) that shows the content loading in real time.

The post is already deleted before you archive it. Check if the URL redirects to a “post unavailable” page. Archive that page anyway, and note the redirect in your log. Then search for the post text in Google or on the platform’s search to find reposts or mirrors. Archive those.

Archive.today is down or slow. It is a volunteer-run service and can be intermittently unavailable. Try again in an hour, or use the Wayback Machine’s “Save Page Now” as a fallback. You can also try a second archiver like archive.org directly.

You need to prove the screenshot is unmodified. Use a tool like the sha256sum command (on Mac/Linux) or Get-FileHash (on Windows PowerShell) to generate a hash of each screenshot file. Save the hash list in your master log. If anyone questions the file, you can recompute the hash and show it matches.

Frequently Asked Questions

Q: Do I need a lawyer to do this?
A: No. This documentation is for your own records or to submit to platform moderators. If you plan to take legal action, a lawyer will appreciate this organized evidence, but you do not need one to start collecting it.

Q: Can I use these screenshots in a public complaint or post?
A: Yes, but redact personal information of third parties (names, faces, addresses) unless they are the person attacking you. Posting unredacted personal data of others could itself be a privacy violation.

Q: How long do web archives keep my saved pages?
A: Indefinitely, in practice. The Wayback Machine has been running since 1996 and has no announced deletion policy for saved pages. Archive.today also retains pages indefinitely, though it is a smaller operation.

Q: What if the smear is in a private group or a direct message?
A: Screenshots are your only option there, since archives cannot access private content. Take screenshots of the entire conversation, including the header showing the other participant’s name and the timestamp. Also screenshot the group info page showing that you are a member.

Q: Should I tell the harasser I am documenting?
A: Generally no. Telling them may cause them to delete everything. Document first, then decide. If you are in a jurisdiction with specific anti-harassment laws, consult a local resource before engaging.

Q: Is it legal to save someone’s public posts?
A: In most jurisdictions, yes. Public posts are publicly available. Saving them for personal documentation is generally considered fair use. However, redistributing them widely may have different implications, so keep your evidence private unless you need to share it with authorities.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →