MBR and GPT are two partitioning schemes. MBR is from 1983, keeps its map in the first 512 bytes with 32 bit numbers, and therefore stops at about 2.2 TB and four primary partitions. GPT uses 64 bit numbers, allows many partitions, keeps a backup table at the end of the disk and checksums both copies.
- The 2.2 TB ceiling is arithmetic, not policy
- MBR has four primary partitions, no more
- GPT keeps a backup table at the far end
- GPT checksums the header and the entries
- MBR2GPT converts without reinstalling
On this page
FundamentalsWhat a partition table actually is
A hard drive or SSD is a long row of numbered sectors and nothing else. It has no notion of partitions, volumes or file systems.
The partition table is a small structure at a known location that says where each partition starts, how long it is, and what kind of data it claims to hold. Everything above it, every file system and every drive letter the operating system shows, is built on that map.
Lose the map and the data is still there, in order, and no operating system can find it. That is the whole reason the difference between these two partitioning schemes matters. Windows calls the choice the partition style of the disk, and asks for it the first time a new drive is initialized.
How MBR stores it
MBR stands for Master Boot Record. The MBR partition table lives in the first sector of the drive, 512 bytes, and does two jobs at once.
The first 446 bytes hold boot code, the small program a legacy BIOS runs to start the operating system. Then come four partition entries of 16 bytes each, and a two byte signature at the end. That is the entire structure.
Computers with BIOS firmware read that sector, run the code, and the code finds the active partition and hands over to the boot loader on it.
Sixteen bytes per partition is not much, and the tight fit is where the limits come from. Each entry stores a starting sector and a length as 32 bit numbers.
The largest number 32 bits can hold, multiplied by the traditional 512 byte sector, is about 2.2 TB. A drive larger than that cannot be described by MBR, and the space past the limit is simply invisible to every operating system.
Four entries is the other limit. The workaround was the extended partition: one of the four is marked as a container holding a chain of logical partitions, which works and adds a layer of indirection that has been confusing people for forty years.
How GPT stores it
GPT stands for GUID Partition Table. The GPT partitioning scheme keeps the same idea and removes the constraints.
The first sector is a protective MBR: a fake MBR describing one partition covering the whole disk, of a type old tools do not recognize. It exists so that a tool that only understands MBR sees a full disk rather than an empty one, and does not helpfully offer to initialize it. This is defensive design, and it works.
The real table starts in the second sector with a header, followed by an array of partition entries, 128 bytes each. Windows reserves room for 128 of them by convention, and the format allows more.
Two properties are worth naming because MBR has neither.
A backup copy. The whole table is written again at the end of the disk. If the primary is damaged, the secondary can restore it.
Checksums. A CRC32 covers the header and another covers the partition array, so corruption is detected rather than silently acted upon. MBR has no integrity check at all, which is why a damaged MBR produces confident nonsense instead of an error.
Each partition also carries a globally unique identifier and a name, so it can be referred to by identity rather than by position, which is what modern operating systems do.
The 2 TB wallThe 2.2 TB wall, and how it shows up
This limit is the reason most people meet the MBR vs GPT comparison at all, and the symptom is confusing until the cause is known.
Attach a 4 TB hard drive, initialize it with the MBR partition style, and Windows shows roughly 2 TB. The rest is not broken, not faulty and not hidden by a setting. MBR simply cannot express a sector number that high, so the space does not exist as far as the partition table is concerned.
The same arithmetic explains a related detail. Some large hard drives report 4096 byte sectors rather than 512, and 32 bits of 4096 byte sectors reaches about 16 TB. This is why a handful of large disks appear to break the rule. It is the same limit with a different multiplier.
The fix is always the same: use GPT. On a data drive that means initializing it correctly, which takes seconds on an empty disk. On a system disk it also means the firmware has to be in UEFI mode, because a legacy BIOS cannot start Windows from a GPT disk.
CompatibilityBIOS, UEFI and operating system support
In practice the MBR vs GPT choice for a system disk is made by the firmware. A computer with legacy BIOS boots from an MBR disk. A computer with UEFI boots from a GPT disk, and reaches MBR only through its compatibility mode, CSM.
Data disks are free of this: any current operating system reads both.
Windows. Microsoft's Windows and GPT FAQ says every version since Windows Vista can use GPT partitioned disks for data, and that booting from GPT is supported only for 64 bit editions on UEFI based systems. A 32 bit edition can use a GPT data drive and cannot start from one.
Microsoft's Windows 11 requirements list "UEFI, Secure Boot capable" as the system firmware, which in practice means a GPT system drive.
Linux. Current distributions support both partition tables. Linux is also the exception to the firmware rule: GRUB can boot from a GPT disk on a BIOS computer if the disk carries a small BIOS boot partition for the boot loader.
macOS. Intel and Apple silicon Macs use GPT, which Disk Utility calls the GUID Partition Map. The Master Boot Record option is there for drives shared with other systems.
On a GPT system disk the boot loader is an ordinary file on the EFI system partition, a small FAT32 partition the firmware reads directly. This is why a UEFI system has no boot code in the first sector to damage, and why Windows creates several partitions on a new system drive.
ConvertingChecking and converting
To see which partitioning scheme a disk uses on Windows, open Disk Management, right click the disk number on the left, and read the menu. If it offers Convert to GPT, the disk is MBR.
If it offers Convert to MBR, it is GPT. The same information is in diskpart with list disk, where a GPT disk carries an asterisk in the Gpt column.
On Linux, sudo parted -l reports the partition table type for each disk, and gdisk -l gives more detail on GPT specifically.
Converting an empty disk is instant and destructive, which is fine when there is nothing on it. Disk Management will do it from the right click menu.
Converting a disk with data used to mean backing up, wiping and restoring. Windows now includes a converter that works in place.
mbr2gpt /validate /allowFullOS
mbr2gpt /convert /allowFullOSValidate first, always, because it names the reason it cannot proceed rather than discovering it halfway. The usual blockers are more than three partitions, no room at the end of the disk for the backup table, or a disk that is not the one Windows booted from.
Three things to do before converting a boot disk. Back it up, because it is a change to the structure that finds everything else. Suspend BitLocker, or the machine will ask for a recovery key afterwards.
And convert the disk before switching the firmware from legacy to UEFI, never the other way round, because a machine will not boot in the mode its disk is not laid out for.
The choiceMBR or GPT: choosing, in one table
For a new disk on current hardware the answer is GPT and there is no case to argue. The question is only live when something in the environment is old, and then it is the firmware and the tooling that decide, never the disk.
| Your situation | MBR or GPT | Why |
|---|---|---|
| A new disk of any size | GPT | The modern default everywhere, with no downside |
| A boot disk on UEFI firmware | GPT | UEFI boots from GPT, and legacy mode is the compatibility path |
| A boot disk on legacy BIOS only | MBR | Legacy firmware will not boot a GPT disk without CSM |
| A data disk on an old machine | GPT | The firmware mode only constrains the disk it starts from |
| Anything over 2.2 TB | GPT | MBR cannot address past the wall, whatever the label says |
| A removable disk for old equipment | MBR | Some appliances and cameras read nothing else |
Read the middle column and notice how narrow the MBR cases are. Two of the six, both of them defined by equipment that already exists rather than by anything you are choosing.
PitfallsWhere people go wrong
Initializing large hard drives as MBR by habit. The dialog offers both schemes and MBR is often the default in older tooling. Two terabytes disappear and nobody notices until the disk fills.
Assuming GPT means UEFI. A data disk can use the GPT scheme on a system that boots in legacy mode without any problem. The firmware mode only constrains the disk the machine starts from.
Trying to boot a GPT disk on legacy firmware. It will not, without CSM, and with CSM it disables Secure Boot. If the goal is a modern secure configuration, the answer is UEFI mode rather than a compatibility layer.
Cloning to a larger drive and expecting the space. If the source used the MBR scheme so does the clone, and the new capacity beyond 2.2 TB is unreachable until the partitioning is converted.
Repairing an MBR by writing a generic one. The generic boot code is fine and the partition entries are not generic. Overwriting them loses the map to everything. This is the operation that turns a boot problem into a data recovery job.
Forgetting the backup table exists. On a GPT disk that reports a damaged table, tools can often rebuild from the copy at the end of the disk. It is worth trying before anything more drastic.
ComparisonMBR and GPT, limit by limit
| Criterion | MBR | GPT |
|---|---|---|
| Introduced | 1983 | Late nineteen nineties |
| Maximum disk | 2.2 TB | 9.4 ZB in theory, no practical limit |
| Primary partitions | Four, extended partitions to work around it | 128 on Windows, more allowed |
| Addressing | 32 bit | 64 bit |
| Backup of the table | None | A second copy at the end of the disk |
| Integrity checking | None | CRC32 on the header and the entries |
| Partition identity | Position in the table | A unique identifier and a name |
| Boots on legacy BIOS | Yes | Only with CSM, and not on every system |
| Boots on UEFI | Only with CSM enabled | Yes, natively |
| Where the boot code lives | In the table itself, 446 bytes | In a normal file on a normal partition |
FAQFrequently asked questions
Should I use MBR or GPT?
GPT, for anything you are setting up now. The only cases for MBR are a boot disk on firmware that has no UEFI mode at all, and removable media for equipment that reads nothing else.
Is MBR or GPT better for a new SSD?
GPT. The partitioning scheme has no effect on speed, but MBR caps the device at about 2.2 TB and allows four primary partitions, and neither limit buys you anything in return.
What is the difference between MBR and GPT?
They are two partitioning schemes. MBR is from 1983, caps a storage device at about 2.2 TB and allows four primary partitions. GPT has no practical size limit, allows many partitions, keeps a backup table and checksums it.
Which partitioning scheme should I choose for new storage?
GPT, unless something specific requires otherwise. It is the modern default on every operating system and has no downside on current hardware.
Why does my 4 TB disk only show 2 TB?
It was initialized as MBR, which cannot address beyond about 2.2 TB. Converting the partition table recovers the rest.
Can I convert without losing data?
On Windows, yes. MBR2GPT converts in place. Back up first and suspend BitLocker, and validate before converting.
Does GPT require UEFI?
Only for the disk the machine boots from. A data disk can be GPT on a legacy machine with no trouble.
What is a protective MBR?
A fake MBR in the first sector of a GPT disk, describing one partition covering everything. It stops old tools from seeing an uninitialized disk and offering to wipe it.
How many partitions can GPT have?
Windows reserves space for 128 by convention. The format itself allows more.
What happens if the partition table is damaged?
On MBR, tools guess, because there is no checksum and no backup. On GPT, the CRC detects it and the backup copy at the end of the disk can usually restore it.
Is the GPT scheme faster?
No. A partition table is read at boot and then not touched. The difference between the two schemes is capability, not speed.
How do I check which scheme a disk uses?
On Windows, right click the disk in Disk Management and read which conversion it offers. On Linux, parted -l reports the partitioning scheme for every storage device.
Can one system have both?
Yes. The boot disk and the data disks are partitioned independently, and mixed setups are common.
Why does MBR only allow four partitions?
Because the table has room for exactly four sixteen byte entries in a 512 byte sector that also holds boot code. Extended partitions were the workaround.
Keep readingRelated concepts
Read next · Firmware and boot What Is a BIOS? Which of these a machine can boot from is decided by the firmware, not by the disk. Open this next12 min- Disks and drives · 12 min SSD vs HDD The medium underneath the partition table, and how the two differ.
- Firmware and boot · 15 min How to Enable Secure Boot, and What to Check Before You Do Converting to GPT is the prerequisite most people meet on the way to Secure Boot.
- Firmware and boot · 10 min UEFI vs BIOS Which firmware mode can boot from each of these, and how to convert.
- Shared storage · 12 min NAS vs SAN The partition table a server writes onto storage, wherever that storage lives.
- Disks and drives · 11 min RAID 5 vs RAID 10 What sits underneath the partition table when there is more than one disk.
- Disks and drives · 9 min FAT32 vs NTFS, and Where exFAT Fits Which file system to put on each partition, and when FAT32, NTFS or exFAT fits.