xsnapshot

A last-known-good record of your PC

Your PC,
on the record.

One local command writes your hardware, packages, config index and wiring to a dated folder. Review it here. Share only the JSON, only if you choose.

Open a snapshot Explore the sample
snapshots/2026-11-05/ Synthetic sample

checkpoint

2026-11-05T12:00:00Z · xsnapshot/v1 · xsnapshot-pc 1.0.0

OS
Example Linux 1
Kernel
6.12.0-example
CPU
Example Eight-Core Processor
Memory
16.0 GiB
GPU
Example GPU
Packages
6
Configs
3
Redactions
4

Folder · sealed by ARTIFACTS.sha256

  • snapshot.jsonJSONPublishable
  • REPORT.md52dede9eLocal
  • ARTIFACTS.sha256sealLocal
  • applied/.bashrc65fb7a4bLocal
  • etc/hostse2049cf6Local
  • etc/os-release269c6090Local
Synthetic sample from fixtures/sample-snapshot.json. Not a real machine. Only snapshot.json can be published.

Capture · Linux

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

Pinned to collector v1.0.0 · uploads nothing · Read the script first

01 — Less rediscovery

One record.
Five ways to use it.

Capture a working setup before a big change. Later, use the record to reason about what you had, what you need and what to try.

A snapshot is a point-in-time record. Memory estimates are not compatibility guarantees; publisher FPS targets are not predictions for your PC. The tools show what they know and what still needs checking.

02 — A clear boundary

Keep the files.
Share the record.

Opening a folder here is local to your browser. Publishing is a separate, explicit step after integrity checks, an identifier scan and your review.

Stays local

Your report and artifact files

  • REPORT.mdRead the privacy section before publishing.
  • ARTIFACTS.sha256Used for local integrity review.
  • etc/ · packages/ · system/ · applied/Supporting files and config bodies stay on your machine.

Only if you publish

The snapshot JSON

Hardware, software inventory and a config index become readable through an unlisted link. No report or artifact bodies are uploaded.

Anyone with the link can read it. Unlisted does not mean private. Keep your delete token to remove the published copy.

03 — Start here

Open your snapshot.
Nothing uploads yet.

  1. 01

    Open locallyChoose the complete snapshot folder, or try the sample.

  2. 02

    Review carefullyCheck the report and scan. Identifiers in the snapshot JSON block publishing; matches in local-only files are listed for you to acknowledge.

  3. 03

    Choose to sharePublish only the reviewed JSON for a link you can keep or share.

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

Drop your snapshot folder

Use the complete snapshots/<id>/ folder for report and integrity review. A single JSON file opens a preview only.

Synthetic. Needs no personal files.

Don’t have a snapshot? Install the collector to capture one locally.

04 — The collector · Linux first

Capture comes before sharing.

Pinned to collector v1.0.0

curl -fsSL https://xsnapshot.app/install.sh | bash
Needs
Linux, git and Python 3.10 or newer.
Verifies
The script fetches the v1.0.0 tag and checks it against that exact commit, byte for byte, before anything runs.
Reads
Allow-listed machine information. It redacts secrets, writes local files and uploads nothing.
Writes
./xsnapshot-data/snapshots/<date>/. Read its REPORT.md before sharing anything.
Coverage
Package inventory is Arch/pacman-specific today, so other distributions get a partial inventory.
Reruns
Same-day reruns keep the existing capture unless you set XSNAPSHOT_FORCE=1.
Is not
A backup or a disk image. It is a record.

Read the script firstCollector source Then open that folder