About MAC Address Generator
A MAC address is a network card's physical identifier, 48 bits (6 bytes) long: the first 3 bytes are the vendor OUI and the last 3 are vendor-assigned. Everything runs on your device with nothing sent to any server. For example, generate a random MAC like 3C:22:FB:xx:xx:xx with vendor-range or fully random prefixes, useful for testing device address filters. Two flag bits decide whether an address is usable, the detail most often missed. The lowest bit of the first byte marks unicast or multicast, and a multicast address cannot serve as a host address. The next bit marks globally or locally administered, so a set local bit means software generated it and it maps to no vendor. For test addresses, set both local and unicast to avoid colliding with real devices. Its relation to the vendor prefix needs separating. The first three bytes of a real adapter address are a registered vendor identifier, so a lookup yields the manufacturer, whereas a random address imitating a real prefix leads a later lookup to a wrong conclusion and confuses network troubleshooting. Keep test addresses in the locally administered range so they read as synthetic at a glance. Separator style varies across systems and breaks on copy-paste. The same twelve hex digits appear colon-separated, hyphen-separated or unseparated, and while most tools accept several inputs, choose the output style matching the target platform or a script matching pattern may fail. Random here is usually pseudo-random rather than cryptographically random. For test data, bulk filling or demos that is enough, but when an address is written into configuration as a device identifier, confirm the source is stable and unique so bulk generation does not collide, and check for duplicates rather than assuming none occur. Finally the boundary: a generated address must not be published as real device information. In public docs, sample code or screenshots, use the reserved documentation ranges or note that the address is an example, which costs nothing and stops a reader copying it into production. Documentation and examples belong in the reserved ranges rather than a prefix that merely looks plausible. The standard sets aside prefixes for docs and samples so a reader can tell at a glance that an address is illustrative, and so sample code copied into production does not collide with real hardware. The locally administered bit is the natural marker, and setting it stamps the address as synthetic. Deduplicate bulk generation rather than trusting probability. The space looks vast, but generating several thousand addresses from a fixed seed or a time-dependent algorithm can collide. Deduplicate as a set afterwards and report any shortfall in count, so the user knows whether the quantity matches the request instead of assuming randomness rules it out.
How It Works Internally
The address is six pairs of hex digits, and the second digit of the first pair carries two flags: one separates unicast from multicast and the other distinguishes globally unique from locally administered. Setting the locally administered bit produces addresses that cannot collide with vendor assignments, which is the standard practice for virtual machines.
An address with the locally administered bit setStarts like x2:xx:xx:xx:xx:xx or x6/xa/xe (second digit of the first pair is 2/6/a/e)Measured on This Page
| Sample output | D6:22:28:6B:9D:B7 (local-admin bit set in the first octet) |
|---|---|
| Formats supported | Colon, hyphen and dotted notation; vendor prefix can be fixed |
When cloning VMs, fix the prefix first and then batch-generate: it makes "two machines ended up with the same address" far easier to debug than pure randomness. The second bit of the first octet is the local-admin bit — set to 1 it means locally assigned, not owned by any vendor.
How to Use
- Open "MAC Address Generator"
- Optionally add a vendor prefix and set the count
- Choose colon, hyphen, dotted or unseparated format
- Pick upper or lower case, then generate the list
- Click a card to copy one address, or copy all
Use Cases
- VM interfaces — Assign non-conflicting MACs in bulk to KVM, VMware, or Docker bridged adapters.
- Re-addressing tests — Generate locally-administered (LAA) addresses to test port security and MAC binding.
- Privacy rotation — Prepare spec-valid random MACs for Wi-Fi randomization to resist long-term tracking.
- Network simulation — Populate unique L2 addresses for many virtual nodes in ns-3, GNS3, and similar tools.
- Firmware placeholders — Use random MACs during embedded development before burning real OUIs at production.
- MAC spoofing scripts — Generate random locally-administered addresses for privacy scripts that rotate the MAC at each boot.
- Test access lists — Produce a range of MACs with specific OUIs to validate port-security and ACL rules on switches.
FAQ
Will generated MACs collide with real devices?
Set bit 2 of the first byte (the locally-administered bit) to 1 to produce an LAA address. These never clash with factory globally-unique (UAA) addresses, making them ideal for testing.
How do I ensure a unicast address?
Set the least-significant bit of the first byte to 0 for unicast; 1 means multicast. This tool defaults to unicast so frames are not treated as broadcast.
Can I fix the first three bytes to a vendor?
Yes, lock a known OUI prefix and randomize the last three bytes. To look up which vendor a MAC belongs to, use our MAC Address Lookup tool.
Which separator formats are supported?
Colon (00:1A:2B), hyphen (00-1A-2B), dotted Cisco style (001A.2B3C), and plain hex with no separator — choose per target system.
Is the randomness reliable?
Bytes come from the browser's cryptographically secure random source, evenly distributed and fit for generating many non-repeating addresses.
Online MAC generator vs desktop software — any difference?
The online version needs no download or install: everything runs locally in your browser with nothing uploaded, so it is as safe as desktop software while working on Windows, macOS, Linux, and mobile alike.
How do I apply a generated MAC to my network adapter?
Windows: Device Manager → adapter Properties → Advanced → Network Address (no separators). Linux: ip link set dev eth0 address NEW. macOS: sudo ifconfig en0 ether NEW. Use a locally-administered (LAA) address to avoid clashing with real hardware.
How do I find which vendor a MAC address belongs to (MAC vendor lookup)?
Use our MAC Address Vendor Lookup tool (/mac-address-lookup.html): paste any MAC to look up the vendor name, country, and registrant from the official IEEE OUI database, with batch support.
What is the locally-administered (U/L) bit and why set it?
Bit 2 of the first byte: 0 means globally unique (factory-assigned), 1 means locally administered (LAA). Random MACs with this bit set live in the LAA space and can never collide with any factory address — Wi-Fi randomization and VM NICs use exactly this class.