WebToSparkBefore a save
The popup shows a cached preview, the last successful save and formats that are still missing. A preview describes cached extraction, not a guarantee of the live page’s complete contents. Duplicate checks run again against the actual documents used for export.
What counts as the same version
Identical page and format variants are skipped by default. Body, comments or source metadata changes can create a substantive version. Capture timestamps and volatile engagement metrics alone do not. Inclusion settings and formats identify separate export variants.
For example, after saving Markdown, requesting Markdown plus JSON writes the missing JSON rather than another identical Markdown file. Use Save another copy when you intentionally want a new file, including a metrics-only snapshot. Originals are not overwritten.
History is a record, not a file browser
History stores metadata separately from the expiring parser cache. Clearing cache preserves history and usage. Removing a history record removes metadata only; it does not delete files or reset allowance.
A recorded path means a save completed there. The extension cannot infer whether you later moved or deleted the file. Files saved before history existed are not automatically discovered or linked.
Handle uncertain results carefully
A smaller capture is flagged instead of being assumed to be a newer complete page. A timeout or lost acknowledgement is unknown, not saved. Inspect the destination before retrying or releasing a pending allowance reservation. Active saves cannot have their reservation cleared.