Does Versionista Save a Full History of Monitored Website Changes?

Short answer: Versionista documents a history of captured page versions that users can compare, but its public materials do not promise that every change is captured, that history is complete, or that captures are retained indefinitely. They also do not publish a fixed retention period. If you need a permanent audit record, confirm retention, export, and deletion terms for your account before relying on it.

What Versionista says it saves

Versionista describes page views that list captured versions and comparison views for reviewing a recent capture against previously collected versions. In its words, users can “compare the newest version of a page to any previously collected versions.” That establishes that captured versions are available for comparison; it does not establish how long each version remains available.

There is also an important distinction between a page changing and a new version being recorded. With keyword-focused monitoring, Versionista can be configured to create a new version only when specified words or phrases are added or deleted. Other changes are ignored for version recording. A history produced with that setting may therefore omit visual, structural, or textual changes that do not match the selected phrases.

What “full history” does not establish

The official homepage, tutorials, and API documentation reviewed for this guide do not specify a maximum history age, a retention duration, a guarantee that all changes are captured, or what happens to stored versions when an account closes. “Full history” is therefore not a documented retention guarantee. The actual policy for a particular account remains an open question for Versionista or Fluxguard.

Do not interpret the one-week public-access period for comparison links in email summaries as a storage limit. That statement describes access to emailed links; it does not say how long versions remain stored inside an account.

Versionista’s current account context

Versionista’s homepage says it is now part of the Fluxguard family, directs new monitoring accounts to Fluxguard, and says existing Versionista accounts remain supported. The page does not give an end date for support or define how long historical captures are retained. Check the service’s current terms and account-specific information before making a retention decision.

The documented Versionista API identifies itself as a pilot API and describes a test endpoint and a watch endpoint for adding a URL to monitoring. The API page reviewed does not document a history-retention policy or a version-export endpoint. That is a limit of the described API documentation, not proof that no other export option exists.

Questions to ask before relying on the archive

How long are captures retained? Ask for the retention period that applies to your account and whether it differs by plan or account status.
What happens after cancellation or account closure? Confirm when stored captures are deleted and whether there is a recovery period.
Can you export the versions? Ask which content and metadata are exportable, in what format, and whether export covers historical captures or only current data.
Does monitoring configuration suppress versions? Check whether focus phrases or other filters mean that changes can occur without a new version being recorded.
How often is a page captured? A history can only show states observed by the monitoring schedule. Confirm the capture frequency and any limits that could leave gaps.
Can you retain your own audit copy? If your requirement is durable evidence, establish a separate export or archival process and test that it captures the pages and metadata you need.

How to preserve your own visual record

A screenshot archive can complement change monitoring when you need a visual record of selected pages. It records the rendered appearance at capture time; it does not by itself prove that every intervening change was observed or provide a complete textual change log. Choose a capture schedule that matches your audit need, keep the original files with timestamps and URLs, and verify that your process succeeds on pages that require cookies, authentication, or JavaScript rendering.

Do-it-yourself with a browser

For a one-off capture, use a browser’s built-in screenshot command or an automation library such as Playwright. This runnable Node.js example saves a full-page PNG. Install Playwright and its browser first with npm install playwright and npx playwright install chromium.

const { chromium } = require('playwright');

(async () => {
  const browser = await chromium.launch({ headless: true });
  const page = await browser.newPage({ viewport: { width: 1440, height: 900 } });
  try {
    await page.goto('https://example.com', {
      waitUntil: 'networkidle',
      timeout: 60000,
    });
    await page.screenshot({ path: 'page.png', fullPage: true });
  } finally {
    await browser.close();
  }
})();

For repeatable archives, add explicit retries and logging, store the capture timestamp and requested URL beside each file, and decide how to handle pages whose content changes continuously. Some sites never reach network idle; in that case, wait for a meaningful selector or use a bounded delay instead. Protect credentials and any screenshots containing personal or confidential data.

Or skip the browser setup

ScreenshotNeo is a website screenshot API: one GET request returns a PNG, JPEG, WebP, or PDF. Its capture workflow accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before the shot; each step can be turned off. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and responses identify the page verdict and billing status in headers. ScreenshotNeo also offers an MCP server with take_screenshot, get_page_info, and capture_pdf tools for AI agents. Every feature is on every plan; 1,000 screenshots a month are free with no card, and paid plans start at $5 for 3,000 shots. See the ScreenshotNeo API documentation.

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

import requests

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

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

These captures can help you keep a visual archive, but they do not replace a provider’s retention terms or guarantee that every change between scheduled captures is observed. Learn more at ScreenshotNeo. Sign up for 1,000 free screenshots a month, with no card required.

Troubleshooting and reliability notes

A change happened, but there is no new Versionista version

Check whether focus phrases are enabled. In keyword-focused monitoring, changes outside the configured words or phrases can be ignored for version recording. Review the monitoring settings and confirm what conditions create a version.

You cannot open an old comparison link from an email

The public comparison links in email summaries are described as temporary for one week. Open the capture from the account interface if it is still available, or ask the provider about access. The link’s expiry does not tell you the account’s storage-retention period.

You need an exact retention answer

The public materials reviewed do not publish a duration. Ask Versionista or Fluxguard for the policy that applies to your account, including export and deletion after cancellation. Do not infer a retention promise from the fact that older versions can be compared.

A browser screenshot script times out

Some pages keep background requests open and never become idle. Wait for a specific content selector, increase the timeout within a reasonable bound, or use a fixed delay after navigation. Record failures explicitly so a missing file is not mistaken for an unchanged page.

A screenshot is blank or incomplete

Confirm that navigation reached the expected page, wait for client-rendered content, and check whether the page requires authentication or consent. For long pages, use full-page capture and verify that lazy-loaded sections were actually rendered before capture.

Performance, reliability, and cost considerations

History completeness depends on observation frequency and capture rules. More frequent captures reduce the time window in which an unobserved change can occur, but increase storage, processing, and review needs. Keyword filtering can reduce noise, but it also narrows which changes become recorded versions. For an audit requirement, define the acceptable observation gap and verify that the chosen schedule meets it.

A self-hosted browser workflow gives control over scheduling and file storage, but you must operate browsers, handle retries and site failures, and retain and secure the outputs. A hosted screenshot API removes much of the browser setup, while each captured image still reflects only a point in time. ScreenshotNeo publishes usage pricing from a free allowance of 1,000 shots per month to paid plans; consult its current documentation for request options and account usage. Neither screenshots nor monitored versions should be treated as a substitute for an explicit retention agreement when durable archival is required.

FAQ

Can I compare a current page with older captures in Versionista?

Versionista describes comparing the newest capture with previously collected versions. Availability of any specific old capture depends on the account and applicable retention policy.

How long does Versionista keep page versions?

The official public materials reviewed here do not publish a retention duration. Ask the provider about the policy for your account.

Does the one-week email link mean versions are deleted after a week?

No. The one-week statement concerns temporary public access to comparison links sent in email summaries, not storage duration inside an account.

Does Versionista currently accept new monitoring accounts?

Its homepage directs new monitoring accounts to Fluxguard and says existing Versionista accounts remain supported. It does not specify how long that support or historical data retention will continue.

Sources

Versionista homepage — current transition information and direction for new accounts.
Versionista, Open Source Intelligence with Versionista — describes comparing recent captures with previously collected versions.
Versionista keyword-monitoring tutorial — explains focus phrase behavior and when new versions are recorded.
Versionista email-alert tutorial — describes the temporary public availability of email comparison links.
Versionista API documentation — describes the pilot API endpoints.