xsnapshot

One link to your PC’s record

Your machine changes.
Your snapshot doesn’t.

One command records your PC in a dated snapshot. Nothing uploads until you publish. Then any assistant can read it from one link.

snapshots/2026-11-10/ Real machine

plazir27

2026-11-10T09:41:56-03:00 · xsnapshot/v1 · xsnapshot-pc 1.0.0

OS
Arch Linux
Kernel
7.2.11-arch1-1
CPU
AMD Ryzen 9 9950X 16-Core Processor
Memory
30.3 GiB
GPU
NVIDIA GeForce RTX 5070
Packages
1537
Configs
674
Redactions
259

Folder · sealed by ARTIFACTS.sha256

  • snapshot.jsonJSONPublishable
  • REPORT.md05eb0e57Local
  • ARTIFACTS.sha256sealLocal
  • applied/.bashrcce445c23Local
  • etc/hosts74179b40Local
  • etc/os-release71ff7a6eLocal
A real machine, captured 2026-11-10.

Capture · Linux

curl -fsSL https://xsnapshot.app/install.sh | bash

Pinned to collector v1.1.0. Uploads nothing. Read the script first

01 — Paste the link

Paste the link.
Ask about your PC.

Give it to any assistant with your question. No need to describe your PC.

One message, for example

https://xsnapshot.app/s/<id>
I just reinstalled. Help me set this PC up like it was here.
  • Set it up like last time.

    Your apps, services, desktop and config files, or the install commands.

  • I am switching systems. Get me close.

    The nearest match for each piece, and what will not carry over.

  • Will this run on my PC?

    A game, an app or a local AI model, checked against your hardware.

  • It worked last month. What changed?

    Paste an older link and a newer one; it points at what moved.

It answers from the record, not from your PC as it is today. Check what matters before you act.

02 — A fixed point

Like a commit,
for hardware and setup.

Your machine moves on. A snapshot stays as it was the day you took it. Take one before and after a big change.

Dated
A folder named for its day, with the exact capture time.
Hashed
Sealed by ARTIFACTS.sha256; each mapped config is hashed.
Unchanging
A published snapshot cannot be edited, only deleted.
Comparable
Compare system fields, packages and config hashes.

03 — For you, too

One record.
Five ways to use it.

Every tool runs in your browser.

Estimates, not guarantees.

04 — A clear boundary

Keep the files.
Share the record.

Stays local

Everything else

  • REPORT.mdRead its privacy section before publishing.
  • ARTIFACTS.sha256The folder’s integrity seal.
  • etc/ · packages/ · system/ · applied/Supporting files and config contents.

Or the same folder in your private repository.

Only if you publish

The snapshot JSON

Hardware, packages, services; config hashes, not contents.

  • 30 daysWithout an account. Then it stops working.
  • 180 daysSigned in; last 10 listed, the 11th replaces the oldest. A username adds /<name>/latest, public to anyone who knows it.

Unlisted is not private: anyone with the link can read it. Your delete token removes it sooner.

05 — Start here

Open your snapshot.
Nothing uploads yet.

  1. 01

    Open locally. Choose the snapshot folder, or try the sample.

  2. 02

    Review carefully. Read the report. Identifiers in the JSON block publishing.

  3. 03

    Choose to share. Publish only the reviewed JSON and get one link.

./xsnapshot-data/snapshots/<date>/the folder the collector writes

Drop the folder here

The full review needs the whole folder. A single JSON file opens a preview only.

Synthetic, no personal files.

No snapshot yet? Install the collector.

06 — The collector · Linux first

Capture comes before sharing.

Pinned to collector v1.1.0

curl -fsSL https://xsnapshot.app/install.sh | bash
Needs
Linux, git and Python 3.10 or newer.
Verifies
The v1.1.0 tag, checked against its exact commit.
Reads
Machine facts, not a backup. Known secrets redacted.
Writes
./xsnapshot-data/snapshots/<date>/. Uploads nothing.
Coverage
Full package inventory on Arch; partial elsewhere.
Your own repo
Optional: xsnapshot-repo init puts the folder in your private GitHub repo; update adds a snapshot. No website.