How to Make a Website Evidence Pack with Screenshots and Page URLs

A useful website evidence pack keeps the page’s relevant content and context together with its source URL and capture date and time. Capture the full relevant page where practical, save a screenshot, add a PDF or HTML copy when useful, then open each file to verify it. Keep an organized index and a secure backup. A screenshot or capture tool cannot guarantee that a court will accept the material; check applicable court or organizational requirements.

What to include in an evidence pack

For each page, preserve enough information for someone else to understand what was captured and where it came from. A practical pack can contain:

Full-page screenshot: include the relevant content and surrounding context. If comments, profile details, a poster identity, or other material explains the page, capture that context too.
Source URL: record the complete page address, including relevant path and query parameters.
Capture date and time: write down when you captured it and the time zone. Keep this information in the index or filename as well as any capture metadata.
PDF copy: useful as a portable, multipage rendering of the page. Check that it contains the material you need.
Saved HTML, when practical: it may preserve more page structure, but locally saved pages can have broken images, styles, scripts, or links. Keep the screenshot as a separate visual record.
Short index: associate each file with its URL, capture time, and a brief neutral description.
Secure extra copy: keep another copy somewhere you can access safely, especially if the material is sensitive.

This is a practical organization method, not a formal evidence standard. The BC Society of Transition Houses recommends including the page URL and capture date and time, and advises collecting the full relevant webpage where possible. Its guidance also notes that a browser’s print-to-PDF function may not capture the whole website. ScreenshotNeo is a website screenshot API and MCP server that can produce screenshots or PDFs; using software to capture a page does not establish legal acceptance.

Step-by-step: capture and organize a page

Identify the exact page. Copy its URL into your notes before capturing. Note any account, post, thread, or surrounding context that helps identify the material.
Decide how much context matters. Capture the whole relevant page where feasible. Expand comments or other collapsed content that is part of the record you need. Avoid cropping away identifying context.
Take a screenshot. Use the device’s built-in screenshot function or a browser capture method. Device shortcuts differ; check instructions for your particular computer, phone, or tablet.
Save a PDF if useful. On a desktop browser, open Print and choose Save as PDF. If available, enable headers and footers to include the page URL and date. Do not assume the PDF is complete: open it and inspect every page.
Save HTML if practical. Keep it alongside the screenshot, but inspect it locally. A saved HTML page may depend on external resources or fail to render as it did online.
Record capture details. Add the exact URL, capture date and time, time zone, and filenames to an index. Record any relevant limitations, such as a page that would not load completely.
Verify the files. Open the screenshot, PDF, and HTML copy. Confirm the intended text and context are visible, the PDF pages are present, and the files open from the location where you will store or share them.
Store a secure copy. Preserve another copy in a location you can continue to access securely. Consider who can access the device, account, or storage containing sensitive material.
Check local requirements. If the pack is intended for a court or organization, check its format and submission rules. Requirements vary; these steps do not determine admissibility or sufficiency.

Capture methods and their tradeoffs

Method	Useful for	Limits and checks
Built-in screenshot	A quick visual record of a displayed page.	Make sure the whole relevant context is included. Record the URL and capture time separately.
Browser Print to PDF	A portable, multipage rendering that may include URL and date in headers or footers.	Print output may omit page content. Inspect the exported PDF rather than assuming it is complete.
Screenshot plus saved HTML	A visual record paired with page structure and text where available.	Locally saved HTML may have broken parts or differ from the live page. Retain and inspect the screenshot too.
Capture software or an API	Repeatable captures, automation, or additional output formats.	Check what the software actually saves and how it handles failures. Product features and metadata are not proof of legal acceptance.

Choose based on page completeness, whether URL and capture time stay attached, how easily another person can review the files, storage and sharing needs, and any court or organizational format rules.

Use clear filenames and an index

Use consistent, descriptive names that connect files without embedding unnecessary sensitive details. For example:

2026-10-04T1430Z_example-com_post-screenshot.png
2026-10-04T1430Z_example-com_post.pdf
2026-10-04T1430Z_example-com_post.html
index.csv

The date in this example is illustrative. Use the actual capture time and a clear time-zone convention, such as UTC. An index can have columns like:

file,source_url,captured_at,timezone,description,notes
2026-10-04T1430Z_example-com_post-screenshot.png,https://example.com/post,2026-10-04 14:30,UTC,Full page screenshot,Comments expanded
2026-10-04T1430Z_example-com_post.pdf,https://example.com/post,2026-10-04 14:30,UTC,Print to PDF,Checked all pages

Keep descriptions factual. If a page was partially unavailable or a PDF omitted material, record that instead of implying the capture was complete.

Practical limitations and safety

Pages change. A capture records what the tool displayed at the time; it does not by itself establish how long content was published or who controlled the page.
Dynamic content may be absent. Lazy-loaded images, content behind interactions, or comments that were not expanded may not appear. Review the capture and note any missing context.
PDF rendering can differ. Print styles can rearrange or omit content. Inspect every exported page and use a screenshot as a separate visual reference.
HTML may not be self-contained. The saved file can rely on online resources that later change or disappear. Test it offline if practical, while retaining the screenshot.
Be careful with sensitive material. Consider who can discover or access local files, cloud storage, or shared devices. Use a secure copy location appropriate to the sensitivity.
Check required formats. Rules depend on the court or organization and the matter. The cited practical guides do not establish universal admissibility or sufficiency.

Or skip the browser setup

For repeatable captures or automation, ScreenshotNeo takes a screenshot or PDF with one GET request. See the API documentation for available options and setup details.

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://example.com/post \
  -o evidence.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://example.com/post"},
    timeout=90,
)
open("evidence.webp", "wb").write(r.content)

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://example.com/post'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(({ writeFile }) =>
  writeFile('evidence.webp', Buffer.from(await res.arrayBuffer()))
);

Keep the page URL and capture time in your evidence index even when a capture is automated, and open the resulting file to check it. ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month with no card.

Troubleshooting

Problem	Likely cause	What to do
Part of the page is missing	The page was longer than the visible area, content was lazy-loaded, or a section was collapsed.	Capture the full relevant page, scroll through it to load content, expand relevant sections, and capture again. Note any content you could not access.
The PDF has fewer details than the live page	Print styles or browser output omitted elements.	Open and inspect the PDF. Use a screenshot alongside it, and keep HTML where practical.
The saved HTML looks broken	It references resources that were not saved or are no longer reachable.	Retain the screenshot as the visual record, keep the HTML copy with the pack, and note the rendering limitation.
The URL or time is missing from a file	The capture method did not add identifying metadata.	Record the exact URL and capture time with time zone in the index and use consistent filenames.
The capture excludes comments or surrounding context	Those sections were collapsed, below the fold, or not included in the selected capture area.	Expand and capture the relevant context. Keep the relationship to the target page clear in the index.
You cannot access the file later	It was stored on a device or account that is unavailable or unsafe to use.	Make a secure additional copy in a location you can continue to access, considering who else can access it.
A court or organization questions the format	Submission rules differ by location and matter.	Ask the relevant court or organization what formats and supporting information it accepts. A generic capture workflow cannot answer that question.

Frequently asked questions

Should I keep both a screenshot and a PDF?

When practical, yes. They provide different views of the page, and the PDF should be checked because print output can omit content. Keep the screenshot as its own file.

Is a screenshot enough to prove a page was online?

A screenshot records a visual appearance, but these practical preservation steps do not establish legal proof, admissibility, or sufficiency. Requirements and the facts of the matter vary.

Should the whole screen or the webpage be captured?

For a webpage record, preserve the full relevant page and its identifying context where feasible. Device guides may address phone or tablet screenshots separately; use instructions for your specific device.

Can I rely on a saved HTML file alone?

That is risky as a practical record because locally saved HTML can have broken parts. Keep a screenshot alongside it and inspect both files.

Sources and scope

This article draws on the BC Society of Transition Houses Technology Safety Project guidance on preserving website content and the Florida Courts-hosted guide on device screenshots and secure copies. The guidance supports practical preservation steps, not a universal legal conclusion. Check local requirements before relying on a pack for a particular proceeding.