Speccy reads hardware and operating-system information from a computer and arranges it into an inventory. It identifies components such as the processor, motherboard, memory modules, graphics hardware, and storage devices. It does not benchmark those parts or repair them. Its purpose is to show what the machine contains, report available sensor data, and save a record for later comparison or sharing.
Hardware scan
The summary page condenses the major components, while category pages expose more fields for each area. Memory information can show installed modules and timings. Storage pages can include drive identity, partitions, and SMART data when the device reports it. Network and peripheral sections describe detected interfaces and attached hardware. A blank field does not automatically mean a component is absent; the device or driver may not expose that value through the interface it reads.
The first analysis can take time while it collects these records. During that analysis, the save commands remain unavailable. Waiting for the scan to finish matters because an early screen may not yet contain the storage or sensor information needed for a support record.
Live readings
Speccy displays temperatures for components that expose compatible sensors. These readings change while the live view remains open. They can help reveal that a processor or drive temperature rose during a workload, but it does not control the fan or change a cooling policy. Missing temperature data can come from unsupported sensors rather than a zero-temperature component.
A single reading also lacks workload context. A useful comparison records whether the computer sat idle, installed an update, or ran a demanding task. It supplies the measurement; it does not decide which temperature range the component manufacturer permits.
Snapshot files
The Save Snapshot command writes a point-in-time record with the .speccy extension. Speccy can load that file later and display the stored hardware state even on another computer. The snapshot does not become a live connection to the original machine. It freezes the values at the moment of capture.
The proprietary snapshot needs Speccy to open it. XML and plain-text exports work better when another program or a support technician needs readable data without Speccy. These formats do not preserve the same interactive presentation. Choosing the output therefore depends on whether the recipient needs a Speccy view or portable text.
Published snapshots
Publish Snapshot uploads a report and returns a random web address. The published report follows the language and temperature units selected in the live view. It does not include the machine’s public IP address. It can still reveal detailed hardware and operating-system information, so treat the link as a shareable diagnostic record rather than harmless anonymous text.
A later launch creates another random address when the user publishes a new snapshot. A saved support link therefore points to that earlier report; it does not track later hardware changes automatically. The user must publish another snapshot and send its new address when the machine state changes.
Frozen records
Loading a .speccy snapshot opens snapshot view. Live sensor graphs do not update there because the file contains stored values. Snapshot view also blocks saving another snapshot and exporting XML. A fresh record requires another analysis of the current computer rather than treating a loaded file as new live data.
