Skip to main content
HWID Checker
hwidbasicshardwarefingerprinting

What Is a HWID and How Does It Work?

Learn what a hardware ID is, which device values it may use, how identifiers are normalized and hashed, and how HWIDs differ from browser fingerprints.

HWID Checker · July 19, 2026 · 7 min read

A hardware ID (HWID) is a value that software uses to distinguish or recognize a device. There is no universal HWID standard: one product may use a motherboard UUID, another may use Windows MachineGuid, and another may hash several identifiers into a vendor-specific fingerprint.

That is why the same computer can have several valid values that are all described as “the HWID.” Before sharing one, confirm which field and format the recipient expects.

What can be included in a HWID?

Software may use one or more of these attributes:

  • Motherboard — SMBIOS UUID, manufacturer or serial number
  • BIOS and chassis — firmware or enclosure serial numbers
  • Storage — physical drive serial numbers or volume identifiers
  • CPU — model information or ProcessorId; ProcessorId is not a unique per-chip serial
  • Network — MAC addresses, which can change or be randomized
  • Operating system — an installation identifier such as Windows MachineGuid or Linux machine-id
  • Graphics and memory — model information or firmware values when available

Some values are firmware-backed, some identify an operating-system installation, and some describe only a component model. Their stability and uniqueness are not equal.

How stable are common identifiers?

| Identifier | Typical stability | Changes when | Important limitation | | --- | --- | --- | --- | | Motherboard SMBIOS UUID | Very high when valid | Motherboard replacement or firmware changes | Can be blank, generic or duplicated by a vendor | | Motherboard serial | Very high when valid | Motherboard replacement | Some devices report placeholder values | | Physical disk serial | High | Drive replacement or firmware changes | Virtual disks and storage controllers may hide it | | CPU ProcessorId | High | CPU replacement | Identifies processor characteristics, not one unique chip | | Windows MachineGuid | Medium | Windows reinstall, image cloning or manual change | Installation-specific, not physically bound to hardware | | MAC address | Medium | Adapter replacement, randomization or software changes | Easy to change and weak as a sole identifier | | Linux machine-id | Medium | Reinstall, image preparation or manual regeneration | Identifies an OS installation rather than hardware | | Browser fingerprint | Variable | Browser, OS, extension, driver or settings changes | Statistical browser identity, not a hardware serial |

A composite can reduce reliance on one weak value, but an exact final hash still changes whenever any included input changes.

How a HWID is generated

Most implementations follow three stages.

1. Collect identifiers

Native software or operating-system commands read the values available on the device. A Windows utility may query MachineGuid and CIM classes; macOS exposes selected values through IOKit and system_profiler; Linux exposes machine and firmware data through files and system utilities.

A normal web page cannot read motherboard UUIDs, physical disk serials or MAC addresses. It can only collect signals the browser exposes, such as user agent, screen properties, time zone, GPU renderer and canvas output.

2. Normalize the values

Raw values may differ in case, spacing, order or punctuation. A stable implementation defines a canonical representation before comparison or hashing:

machine_guid:6f9619ff-8b86-d011-b42d-00c04fc964ff
smbios_uuid:3f2504e0-4f89-41d3-9a0c-0305e82c3301
disk_serial:sn123456

Normalization must also define how to handle missing values, generic firmware strings, multiple network adapters and virtual devices.

3. Hash or compare

The normalized values may be passed through SHA-256 to create a fixed-length digest. A secure hash does not directly reveal the original strings, but it does not make weak inputs unique and does not prove that the data came from authentic hardware.

A single composite SHA-256 hash cannot identify which component changed. If legitimate upgrades must be tolerated, the system needs protected component-level evidence, a weighted matching policy or a device reactivation process.

Hardware ID vs browser fingerprint

These are related but different concepts:

| Signal | Identifies | Available to a normal website? | Typical persistence | | --- | --- | --- | --- | | Hardware or firmware identifier | A component or device attribute | No | Often survives browser and OS changes | | OS installation ID | One operating-system installation | No | May change after reinstall or image preparation | | Browser fingerprint | A browser environment | Yes | Can drift after software or setting changes | | IP address | A network connection | Visible to the server | Changes with network or provider |

The online fingerprint generator therefore creates a browser fingerprint, not a motherboard UUID or disk serial. Use the Windows utility or documented OS commands when you need device or firmware identifiers.

Common HWID formats

| Format | Example | What the shape tells you | | --- | --- | --- | | UUID / GUID | 3f2504e0-4f89-41d3-9a0c-0305e82c3301 | A standardized 128-bit layout, not proof of hardware origin | | SHA-256-like hex | 64 hexadecimal characters | Consistent with a SHA-256 digest, but the algorithm and inputs are unknown | | MD5-like hex | 32 hexadecimal characters | Consistent with a legacy digest | | MAC address | 00:1B:44:11:3A:B7 | A network-interface address that may be changed or randomized | | Serial number | Vendor-specific text | Meaning and validation depend on the manufacturer | | Composite ID | Prefixes and separators | A vendor-defined structure containing one or more fields |

Use the HWID Validator and Parser to detect likely formats and inspect recognizable sections. A valid-looking string is not proof that the value is authentic, unique or tied to a particular device.

How software uses HWIDs

Software licensing

A vendor may associate an activation with a device-derived identifier. On later checks, the software compares the current evidence with the recorded activation. Good systems provide deactivation, recovery or upgrade handling instead of permanently locking a customer out after one component change.

Read HWID-Based Licensing: Activation and Hardware Changes for implementation details.

Device trust and fraud signals

A device fingerprint can be one signal in a broader risk decision. Account history, network reputation and behavior are usually considered as well; a HWID alone is not proof of a person’s identity.

IT inventory and support

IT teams can associate selected component identifiers with managed assets. Support systems can attach a consistent device reference to logs and tickets, while keeping the full environment report separate.

Anti-cheat enforcement

Some publishers may include a device fingerprint in enforcement decisions. Exact inputs and weighting are usually private. The HWID Ban Checker compares reported behavior with common account, network and hardware-ban patterns, but it cannot access or confirm a publisher’s records.

What happens when hardware changes?

The result depends on the inputs:

  • Replacing a motherboard changes motherboard-derived values.
  • Replacing a physical drive changes its serial but not necessarily MachineGuid.
  • Reinstalling Windows commonly changes installation-specific identifiers but not firmware serials.
  • Changing a network adapter or enabling MAC randomization changes network values.
  • Updating a browser, extension, driver or privacy setting may change a browser fingerprint.

Systems that require continuity should document their matching rules and provide a legitimate recovery path.

Privacy considerations

A persistent device identifier may be personal data when linked to a person, account or activity. Collect only the values needed for a defined purpose, avoid storing unnecessary raw serials, explain retention, and protect any server-side representation.

The browser validator and parser run locally. The optional JSON API receives identifiers deliberately submitted to it. See the privacy policy for the complete data-flow explanation.

How to find or check an identifier

Frequently asked questions

Is a HWID the same as a serial number?

Not necessarily. A serial number is one possible input. A HWID may be a firmware UUID, installation ID, raw serial or hash built from several values.

Can two devices have the same HWID?

Yes. Inputs can be blank, generic, cloned or duplicated. A long hash reduces accidental digest collisions but cannot add uniqueness that was absent from the source values.

Can a website read my hardware ID?

A normal website cannot read motherboard UUIDs or physical disk serials. It can create a browser fingerprint from permitted browser signals.

Does reinstalling Windows change a HWID?

It changes installation-specific values such as MachineGuid, but normally does not change firmware-backed motherboard or physical-drive serials. A vendor-specific composite changes only when one of its selected inputs changes.

Can I reset a HWID?

There is no universal HWID to reset. For licensed software, use the vendor’s deactivation, device-management or support process rather than attempting to spoof identifiers.