MXBK

Incremental Backup Tool: Saves directly to disk • Locally Usable Copy
Designed to produce a reasonable facsimile of your Squarespace website for recovery of images, text content & layouts. (Videos & Audio files are NOT Downloaded: placeholders are visible where they would be.Settings are Auto-Saved.

Status: Ready — Select Folder & Validate first, then START Idle ☁ Cloud x0
Pages saved: 0
Assets saved: 0
Cloud Recoveries Made: 0
Custom Rules Applied: 0
Passworded Pages Saved: 0
Passworded Pages Requiring Validation: 0
Total Data Processed: 0 B
Time Elapsed: 00:00:00
Folder Access Pending
Write Test Pending
Login Session Pending
Run validation to prepare the backup environment.
BACKUP SETTINGS
Below are several options designed to accommodate different use cases. IMPORTANT: CSS files are always downloaded and recursively rewritten for the downloaded copy wherever possible; unresolved code and pages stay online. Your backup will link to live pages for any missing offline equivalents.
Selected-Pages Mode:
Crawl only specific page/path scopes (includes home + shared env assets)
Use sitemap.xml discovery for unlinked pages
(ON by Default) IMPORTANT: Pages marked noindex/private or 'Hide from Search Engines' will likely be absent from the sitemap.xml listing. Use the 'Include Pages' option to add these hidden pages to the backup queue.
Include member pages using your existing logged-in session cookies
If you log in as a member, such that you are able to see your member pages from the FRONT end of your site (as a user), MXBK will also be able to back up those pages for you. (FYI: there is no data sharing or mining at play here, the app is simply using your personal browsing session to access exactly what a member would with their login. This lasts only for the duration of your backup sessions.)
Skip Passworded pages which have not been validated with option to re-run/validate at the end of process).
If set to OFF: the system progressively prompts you to visit and login into password-protected pages as they are visited through the backup process. You may also skip any page by simply tapping 'Continue' without validating. Alternatively, set this to ON to skip the step-by-step; you will still have a chance to validate and retry them at the end the process.
Use this to append known pages that may be missing from sitemap discovery, such as pages hidden from (or otherwise blocked by SEO crawls, etc).
Use Preset Exclusion Rules (recommended)
Enforced by default (to reduce duplicate/archive backups): these URL syntaxes are generally omitted.
    Export rendered site code snapshots (head/footer/scripts/styles) to /★-custom-header-footer-css/
    Allow Remote Scripts (Experimental)
    Keep external JavaScript dependencies for advanced interactive features.
    Default OFF (Recommended) This produces a pure offline backup. FYI: some scripts cannot work offline.
    Show offline backup banner
    Adds the black strip + gold line + OFFLINE BACKUP stamp to saved pages.
    Fallback to live site when local file is missing
    If OFF, missing/unwritten local pages/assets will not defer to live URLs (they may break offline instead).
    Custom Code Transformer & Remover
    Define rules to find and modify/remove code during the save process.
    TRANSFORMER FOOTNOTE: Transformations are applied to ALL matches found in the file. Please use full lines of code as your "Find String" to ensure you don't accidentally delete or modify unrelated parts of the site.
    Use Cloud Assist for failed assets (requires set up)
    OFF by default. If enabled, cloud assist is attempted only after normal retries fail.
    Cloud Assist — more info & setup
    What it does
    • Runs only after local retries fail.
    • Restricted to your site + Squarespace-family hosts.
    • Helps recover CORS-blocked assets in browser-only backups.
    • If cloud endpoint is unavailable, backup still continues (assets stay remote).

    Backend options
    You can use a Cloudflare Worker endpoint (recommended), or an equivalent proxy endpoint backed by R2, S3, or similar infrastructure — as long as it enforces an allowlist and returns asset bytes safely.

    Quick setup
    1) Create endpoint route like /fetch?url=....
    2) In MXBK Javascript Code set:
    const CLOUD_FETCH_ENDPOINT = "https://<yourproxyurl.com>/fetch";
    3) In your cloud app add allowlist env var (e.g. ALLOW_HOSTS):
    yourdomain.com,www.yourdomain.com,*.squarespace.com,*.squarespace-cdn.com,*.sqspcdn.com
    Not tested yet.
    Waiting to run checks...
    Runtime settings loaded.
    🔒 Password validation required
    Open and validate this page, then come back & click Continue.
    |