Webpage Screenshot vs PDF Archive: Which Is Better for Evidence

Neither a webpage screenshot nor a PDF archive is inherently better evidence. A screenshot gives you a quick visual record of a particular browser view. A PDF is often easier to read, print, and share. Both are rendered snapshots: neither alone preserves all of a site’s structure, linked resources, dynamic behavior, or the circumstances of capture.

If the question depends on what was visible, keep a screenshot or PDF as a readable exhibit. If it depends on links, page resources, or the ability to reconstruct more of the site later, preserve a suitable web archive as well. Record how and when each capture was made, retain the original, and document its handling. Format alone does not establish authenticity or determine whether a court will accept or rely on an item.

1. What each format preserves

Format	Useful for	Limits
Screenshot	A fixed visual record of the browser view at capture time; quick to review and attach as an exhibit.	Does not automatically include the rest of the page, linked files, hidden content, or underlying context. It is static and does not retain hypertext functionality.
PDF rendition	A convenient document for reading, printing, and sharing the rendered page.	Captures only what the conversion rendered. Page functions can be lost; complex sites and large amounts of content may not be suitable, and some formats or components may need separate acquisition.
Web archive or capture	Preserving resources and relationships for later review or reconstruction, depending on capture scope and completeness.	May require a replay tool or viewer. An archive format alone does not establish who captured the material or when.

The National Archives and Records Administration (NARA) says static screenshots do not retain hypertext functionality and are not accepted for permanent web-content transfer under its guidance. Its PDF web-capture guidance says rendered content becomes static PDF content, other page functions such as image captions may be lost, and the method is not suitable for complex sites or large amounts of content. These are archival transfer guidelines, not a universal court rule. [NARA web content guidance]

NARA lists WARC 1.0 and 1.1 among preferred file formats. A WARC-compatible capture may fit a preservation workflow when resources and context matter, but completeness still depends on what the capture actually collected. [NARA file-format tables] [NARA guidance on managing web records]

2. Choose a capture based on the question

• “What did this page look like?” Save a screenshot for a concise visual record. A PDF can be a useful reading copy if the rendered page spans multiple pages or needs printing.
• “What did the page link to, or how was it structured?” Capture relevant resources and context with a web-archiving workflow, then keep a screenshot or PDF as a companion exhibit.
• “What changed over time?” Preserve separate captures with their dates, source URLs, and process notes. A single image or PDF cannot show a change history on its own.
• “Can I prove when and how this was captured?” Neither file type answers that by itself. Keep provenance and handling records, and follow applicable organizational procedures and legal advice.

For NARA’s definition and discussion of web-record integrity, see its web records guidance. It defines integrity as a record being complete and unaltered. That is a records-management principle; it does not mean a particular screenshot or archive automatically proves its own completeness.

3. A practical capture and documentation workflow

1. Define the scope. Identify the exact page, relevant state, and question the capture should answer. Note whether scrolling, expanding content, signing in, or other interaction is necessary.
2. Record the source and time. Save the complete URL and capture date and time. Mark each timestamp as UTC or local time, and identify the time zone where useful.
3. Record the process. Note who captured the page, the tool or method used, what was included, and anything that failed to load or required interaction. Record relevant browser or capture settings if they affect the result.
4. Keep original files. Preserve the original screenshot, PDF, or archive. Create a separate working or sharing copy for cropping, annotation, redaction, or conversion, and record each transformation.
5. Capture more than the rendered view when needed. Preserve relevant resources, links, and context with an appropriate web-archiving process if the issue requires them. Consider a WARC-compatible workflow when it fits the scope and retention need.
6. Track integrity and custody. Where appropriate to the stakes and procedure, record file hashes and access or custody events. A hash can help detect later changes to a file; on its own, it cannot prove what the source page contained or the circumstances of capture.
7. Store according to the stakes. Protect the master copy and keep traceable working copies and backups under the applicable retention process. A secure managed server can meet a controlled-storage need; a physical medium is not inherently required.

RFC 3227 recommends detailed notes about discovery, collection, handling, and custody, and says to state whether timestamps are UTC or local time. It also says checksums and cryptographic signing may help preserve a strong chain of evidence where feasible. The RFC is collection guidance, not a jurisdiction-specific legal test. [RFC 3227: Guidelines for Evidence Collection and Archiving]

UK Defence Science and Technology Laboratory digital-imaging guidance describes maintaining a documented, protected master and traceable working copies. Its scope is police and criminal-justice digital imaging; treat the master-copy principle as a process reference rather than a universal webpage-evidence rule. It allows secure server storage when controls and traceability are satisfied. [Digital Imaging and Multimedia Procedure v3.0]

4. Capture a readable screenshot with ScreenshotNeo

A screenshot API can produce a repeatable visual capture without requiring you to set up browser automation. ScreenshotNeo is a website screenshot API and MCP server for developers. A screenshot is still only the rendered view; if the matter requires page resources or archive context, preserve those separately. See the ScreenshotNeo site and API documentation.

Example: request a full-page PNG of the page, then keep the returned file with your capture notes. Use the actual target URL and handle the API key as a secret.

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://example.com \
  -d full_page=true \
  -d format=png \
  -o page.png

For this evidence-oriented example, preserve the original response and record the request settings and capture time. ScreenshotNeo’s response includes page-verdict and billing headers; save relevant response metadata with your notes. Do not treat those headers as proof of legal authenticity.

Python

import requests

response = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={
        "access_key": "YOUR_API_KEY",
        "url": "https://example.com",
        "full_page": "true",
        "format": "png",
    },
    timeout=90,
)
response.raise_for_status()

with open("page.png", "wb") as image_file:
    image_file.write(response.content)

print("Page verdict:", response.headers.get("X-Page-Verdict"))
print("Billed:", response.headers.get("X-Billed"))

Node.js

const query = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://example.com',
  full_page: 'true',
  format: 'png',
});

const response = await fetch(
  `https://api.screenshotneo.com/v1/shot?${query}`
);

if (!response.ok) {
  throw new Error(`Screenshot request failed: ${response.status}`);
}

const image = Buffer.from(await response.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('page.png', image));

console.log('Page verdict:', response.headers.get('X-Page-Verdict'));
console.log('Billed:', response.headers.get('X-Billed'));

Capture a PDF rendition

Use PDF output when a document is more useful for reading or printing. A PDF rendition is not a web archive and may omit functions or components that were not rendered.

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://example.com \
  -d format=pdf \
  -o page.pdf

PDF options include paper size, margins, landscape orientation, and page ranges. Consult the ScreenshotNeo documentation for supported parameter names and values. Select settings that match the content and retain them in your process notes.

Capture considerations and available options

For visual records, choose settings deliberately and note them. ScreenshotNeo supports full-page capture with lazy images loaded, CSS-selector element capture, dark mode, 12 device presets or a custom viewport, retina scale, custom CSS and JavaScript, clicking an element before capture, hiding selectors, waiting for a selector, a delay, or network idle, custom headers, cookies and user agent, timezone and geolocation, transparent backgrounds, image resizing, and request or resource blocking. These controls can change what appears in the result, so capture settings belong in the notes. Features that alter the page, such as hiding elements or running custom scripts, should be used only when they match the purpose and are disclosed in the record.

The API also supports caching with a chosen TTL, signed links for public image tags, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API, and an OpenAPI spec. For a time-sensitive record, decide whether a cached result is appropriate and retain response metadata. Consult the docs for exact options and behavior.

5. Or skip the browser setup

ScreenshotNeo can return a screenshot with one GET request. This example saves a PNG:

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

Cookie banners are accepted like a visitor and more than 60 known consent platforms, newsletter popups, and chat widgets are removed before the shot; each cleanup step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers say which page verdict and billing status applied. An MCP server lets AI agents, including Claude, Cursor, and any MCP client, take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.

6. Troubleshooting capture problems

Problem	Possible cause	What to do
Important content is missing from the image	It was below the captured viewport, lazy-loaded, hidden, or available only after interaction.	Use full-page capture or capture the relevant element; wait for a selector or required delay, and document interactions and settings.
The page looks different from what a person saw	Responsive layout, device viewport, dark mode, location, cookies, or user-agent differences changed the rendered state.	Record the capture environment and set an appropriate viewport and context. Keep the resulting file and notes together.
A cookie banner, popup, or chat widget is absent	A cleanup feature removed it, or the site did not show it in that session.	For a record of the clean page, note the cleanup behavior. If the banner itself is relevant, turn off the corresponding cleanup option in the capture settings and record that choice.
The capture is blank or timed out	The target did not finish loading, presented a bot check, or was otherwise unavailable to the capture.	Check the page verdict and response, confirm the URL is accessible, and retry with a suitable wait condition. Preserve notes about unsuccessful attempts when material.
The PDF omits an image, caption, or page behavior	The conversion rendered static content and did not preserve every function or component.	Keep a screenshot for the visible view and separately capture relevant resources or use an appropriate web archive workflow.
The file cannot establish capture time or integrity	Image and PDF metadata alone may not document the source, process, or custody.	Maintain a separate capture log with URL, timestamp basis, operator, process, original file, transformations, hashes where appropriate, and handling history.

7. Reliability, performance, and cost

Evidence capture is most reliable when the procedure is repeatable and records failed attempts as well as successful ones. Dynamic content can vary by time, location, session, and interaction. A delay can help with slow content, while waiting for a specific selector or network idle can better match the page state you need; the right condition depends on the site. Full-page captures may take longer and produce larger files than viewport captures, particularly when pages load many images. Capture only the scope needed, while preserving additional context where the issue calls for it.

Keep an original master, make working copies for annotations or redactions, and retain notes and relevant response metadata. Checksums can help detect changes to a saved file after capture, but they do not independently establish the page’s source or the time it was captured.

ScreenshotNeo offers 1,000 shots per month free with no card. Paid plans are Starter $5 for 3,000, Growth $15 for 15,000, Pro $39 for 60,000, Scale $99 for 250,000, and Business $249 for 1,000,000; yearly billing gives two months free. Every feature is on every plan. Only clean shots are billed: bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing. These are service pricing and billing terms, not a guarantee that any capture is complete or suitable for a particular proceeding.

8. Frequently asked questions

Is a screenshot enough to prove what a website said?

It may be a useful visual record, but the image alone does not preserve the complete page or establish its capture circumstances. Whether it is enough depends on the issue, required foundation, and applicable procedure.

Should I keep both a PDF and a screenshot?

That can be useful when a screenshot records a particular browser view and a PDF is easier to distribute or read. Keep the original files and document how each was produced.

Does a WARC file prove authenticity?

No. WARC is an archival format. The capture process, scope, provenance, integrity controls, and handling still need documentation.

Will a hash prove the page was online at the recorded time?

No. A hash can help show whether the file changed after the hash was made. It does not by itself prove the source content, capture time, or who performed the capture.

Does this workflow guarantee a court will accept the capture?

No. The cited archival and collection guidance does not establish a universal admissibility test. Follow the rules and advice applicable to the specific jurisdiction and proceeding.

Sources and scope

This article draws on NARA’s web records and file-format guidance, RFC 3227, and UK digital-imaging guidance. These sources describe records preservation and evidence-handling practices within their stated contexts; they do not decide how every court will evaluate a webpage capture. For a live dispute, follow applicable organizational retention procedures and obtain jurisdiction-specific legal advice.