Your questions
answered

WebMoment preserves how Pages evolve by turning each Capture into a permanent Moment in a Timeline.

A Responsive or Full Responsive Capture creates one Moment, even when it includes Desktop, Tablet and Mobile Screenshots. It uses one Moment from your plan, not one per viewport.

The web constantly changes. Launches disappear, pricing changes, redesigns and experiments are lost forever. WebMoment preserves those changes as permanent visual history.

The first Capture creates a Page and Moment; every later Capture extends its Timeline.

No. Pages are created automatically the first time a URL is captured.

We’d be glad to help. [Contact us](/contact) and tell us what you’re preserving.

Visit the [Roadmap](/roadmap) to submit an idea, vote on existing requests and follow their progress.

Use [Report a problem](/report-error) to share what happened and help us investigate.

A Capture is the action that preserves a Page. Every successful Capture creates exactly one immutable Moment.

A Moment is the complete historical record of a Page at one point in time.

No. A Screenshot is only one visual artifact inside a Moment. A Moment preserves much more than the image, including Replay, Web Intelligence, Execution Metadata and the exact Capture configuration used to preserve that point in history.

No. Moments are immutable. Once created they become permanent historical records.

A PARTIAL Moment indicates that WebMoment successfully preserved the Page but one or more optional artifacts, such as Replay, could not be generated.

A Timeline is the complete visual history of a Page. Every new Moment extends that Timeline.

No. Every Timeline belongs to exactly one Page.

Every manual Capture and every Tracking execution adds another Moment.

Tracking creates new Moments on a schedule and extends a Page's Timeline.

No. Tracking preserves visual history; it is not an uptime monitoring service.

Hourly, Daily, Weekly and Monthly.

No. Tracking intentionally abstracts execution times because its purpose is building historical Timelines rather than performing real-time monitoring.

Yes. Every Tracking execution consumes Moments exactly like a manual Capture.

Replay lets you explore a preserved Moment interactively; it is not a video.

Replay renders the archived Page again, so browser and runtime differences may change how it looks compared with the Screenshot.

Some websites depend on runtime behaviors that cannot always be reproduced outside their original environment. Authentication flows, expired sessions, cookies, localStorage, IndexedDB, service workers, API calls, anti-bot protections and third-party integrations can all influence how a Page behaves after it has been preserved.

Yes. Some websites personalize their behavior using cookies, localStorage, sessionStorage or other browser storage mechanisms. Pages that depend on visitor-specific data may display differences or disable certain features when replayed.

In many cases, yes. Replay preserves the Page as a self-contained document, but its original JavaScript may still execute. Depending on how the site was built, those scripts may expect live APIs, backend services, authentication or browser features that are no longer available, which can affect some interactive functionality.

Compare shows how two Moments from the same Page differ.

No. Compare only works between two Moments belonging to the same Page.

Collections group related Pages without merging their Timelines.

Yes. A Page may belong to any number of Collections without duplication.

Only the Collection is removed. All Pages and their Timelines remain unchanged.

Sharing publishes existing history without duplicating or transferring ownership. Depending on the resource, Shares can either remain live as history grows or preserve a fixed historical snapshot.

Live Shares continue evolving as history grows. Snapshot Shares always represent a fixed historical state.

A Timeline Share publishes the complete Timeline of a Page and automatically includes future Moments.

A Moment Share publishes one specific Moment that never changes.

Yes. Passwords belong to the Share itself, not to the underlying resource.

Yes. Start with the Free plan and upgrade any time from Settings → Billing.

Usage is measured in preserved Moments, not storage size.

Plans define limits for Moments, Tracking, Collections, Capture quality, Sharing capabilities and other Workspace features.

New Captures and Tracking pause until your next billing cycle or an upgrade. Enterprise plans are not automatically suspended.

No. Monthly New Moments and Total Preserved Moments are separate counters. Deleting a Moment reduces your total preserved history, but it does not restore the Monthly New Moments quota because that quota counts every new Moment created during the current billing cycle.

You can cancel at any time from Settings → Billing. Your current plan remains active until the end of the billing period.

Fees are non-refundable unless required by law or stated in a written agreement.

Storage is an implementation detail. WebMoment measures the value you preserve through Moments.

A Workspace owns Pages, Collections and Shares while defining collaboration, permissions and billing.

Owner, Member and Viewer (Enterprise plan).

Yes. You can upgrade or downgrade from Settings → Billing. Changes take effect as shown before you confirm them.

Yes. You can create additional Workspaces when your plan supports them. Each Workspace has its own Pages, Timelines, members and billing.

Yes. Invite teammates from your Workspace settings. The number of members you can add depends on your plan.

A downgrade may reduce limits or remove access to plan-specific features. Review the change before confirming and export anything you need before it takes effect.

A Job is a temporary execution resource that coordinates a Capture. It never becomes part of a Page's historical record.

It is the immutable copy of the Capture configuration permanently stored inside every Moment.

Web Intelligence is the publicly observable information preserved during a Capture, including SEO metadata and detected technologies.

WebMoment sends `moment.created` when a Capture creates an INITIAL Moment, `moment.updated` while it is processing or PARTIAL, `moment.completed` when it is COMPLETE, and `moment.failed` when the Capture cannot preserve it. `moment.deleted` is sent when the Moment is removed.

Screenshot URLs become available in `moment.updated` after WebMoment preserves them. When a Moment reaches COMPLETE, `moment.completed` also includes `replayUrl` when Replay is enabled; it points to the preserved `index.html` for that Moment.