Plan without losing the thread
A hardware decision often crosses several calculators. A gaming build may start in the PC Builder, move through GPU comparison and PSU sizing, then return days later. A NAS plan may pair capacity with power cost. Hardware Projects keeps the goal, constraints, supported tool inputs, and dated references under one local project ID.
A saved part list is not a compatibility verdict. Each connected tool keeps its own result and says what it checked; the project only keeps those results together, beside a five-point checklist (clearance, connectors, BIOS support, memory support and PCIe lane sharing) for the checks the manuals and the case itself have to answer.
Choose the right way to move a project
Send a limited snapshot
Review the title first. A limited snapshot retains the title, type, product references and supported tool inputs, along with the original dates, source ID and revision. A name entered as the title or as a Power Cost device name can identify you.
The link is not encrypted. It omits the use case, constraints, diagnostic text, evidence and compatibility checklist. Opening it creates an unsaved preview with a fresh ID and revision 0, preserving the original dates. The recipient must choose Save as a new project to keep that preview.
Keep a full backup
Download full JSON when you need the supported private fields and compatibility records as well as the calculator state. Keep the file private.
Both downloads and snapshots can include current form edits before you save them on this device. Review those edits too.
Importing a full file opens an unsaved preview with a new ID. It keeps supported private fields and compatibility records but drops the old PC Builder reference.
Import cannot replace an existing project. Choose Save as a new project to keep the preview.
Know when a save happens
A new dashboard project starts unsaved. By contrast, Create project inside a connected calculator saves immediately, and Import PC Builder saves writes new Hardware Projects copies immediately while keeping the original builds. File imports and snapshot links use the preview step described above.
Clear the local copy
Projects have no automatic expiry, but browser cleanup can remove them. Another device can receive a full file or a limited snapshot; there is no account sync.
Removing a local project cannot recall a downloaded file, a copied link, or someone else’s saved copy. If browser storage is unavailable, full, or corrupt, the workspace reports the failure instead of replacing the stored record.
Connected tool links can put calculator inputs and the local project ID in a URL query. Opening that URL sends those parameters to hosting. The ID alone does not transfer private notes.
See the privacy guide and actual field examples before moving a project.
Start with a focused route
Start with one decision.
- For a new gaming PC or upgrade, start with PC Builder, compare the exact GPUs you are considering, then run the saved load through the PSU calculator.
- For a storage server, start with the usable-capacity and fault-tolerance tradeoff in the NAS calculator, then carry its state into the power-cost calculator.
- For intermittent faults, open the Diagnostic Workbench from a diagnostic project. Record the symptom, display or hardware path, recent change, tests, and outcome without placing those notes in a shared snapshot.
- For ECC or expansion decisions, attach the dated result from the AM5 ECC checker or NVMe expansion checker. Keep the manufacturer evidence and its stated scope beside the project.