Basics

MBR vs GPT: Which Partition Style Should You Use?

Updated October 2, 2026 •7 min read

Every drive needs a map that says where its partitions begin and end. There are two formats for that map: MBR (Master Boot Record) and GPT (GUID Partition Table). The MBR vs GPT choice usually comes up when you add a new drive, install Windows, or hit a strange 2 TB limit. For most people today the answer is simple: use GPT. But how you switch between them matters a lot, because a wrong conversion is one of the more common ways people erase their own data.

MBR vs GPT at a glance

	MBR	GPT
Introduced	Early 1980s (IBM PC era)	Late 1990s, with Intel’s EFI (now UEFI)
Max disk size	2 TB (with 512-byte sectors)	Far beyond any current drive
Partitions	4 primary (or 3 primary + 1 extended with logical drives)	128 by default in Windows
Boot firmware	BIOS / legacy (CSM)	UEFI
Partition table copies	One, in the first sector	Primary at the start, backup at the end
Integrity checks	None	CRC32 checksums on header and table

What MBR is

The Master Boot Record lives in the very first sector of the disk (sector 0). That single 512-byte sector holds a small piece of boot code plus a partition table with room for four entries. To get more than four partitions, one of them can be an “extended” partition containing logical drives.

MBR stores partition locations as 32-bit numbers, which caps the addressable space at 2 TB on drives with 512-byte sectors. Put a 4 TB drive on MBR and Windows will typically only let you use about 2 TB of it; the rest shows as unallocated.

MBR is tied to the old BIOS boot method. It still works, but it’s a legacy format.

What GPT is

The GUID Partition Table is part of the UEFI standard that replaced BIOS. Its key differences:

Huge disk support. GPT uses 64-bit addresses, so disk size isn’t a practical concern.
More partitions. Windows allows 128 partitions on a GPT disk by default, with no extended/logical juggling.
Redundancy. GPT keeps a primary header and partition table at the start of the disk and a backup copy at the very end.
Error detection. Both copies carry CRC32 checksums, so the system can tell when the table is damaged rather than trusting bad data.
A “protective MBR.” Sector 0 of a GPT disk holds a dummy MBR entry covering the whole disk, so older MBR-only tools see the disk as occupied instead of empty.

Which should you use?

Any modern PC booting Windows 10 or 11: GPT with UEFI. Windows 11 requires UEFI, which means a GPT system disk.
Any drive larger than 2 TB: GPT. MBR can’t use the space beyond 2 TB.
Data drives: GPT, unless you need the drive to work with a very old computer or device that only understands MBR.
Older BIOS-only computers: MBR for the boot drive, because a BIOS can’t boot Windows from GPT.

Macs use GPT (shown as “GUID Partition Map” in Disk Utility), and current Linux distributions handle both.

How to check whether a disk is MBR or GPT

Disk Management

Right-click Start and choose Disk Management.
Right-click the disk label on the left (for example, “Disk 1”), not a partition, and choose Properties.
Open the Volumes tab and look at Partition style: it will say Master Boot Record (MBR) or GUID Partition Table (GPT).

Command line (diskpart)

Open Command Prompt as administrator and run:

diskpart
list disk

In the output, a disk with an asterisk (*) in the Gpt column is GPT; no asterisk means MBR. Type exit to leave diskpart. Only use list commands here; other diskpart commands can change or erase disks.

Converting MBR to GPT

There are two very different ways to convert, and only one of them keeps your data.

The safe way: MBR2GPT (system disks)

Windows 10 version 1703 and later include MBR2GPT, a Microsoft tool that converts a Windows system disk from MBR to GPT without deleting partitions. It’s designed for moving a PC from BIOS to UEFI boot.

Back up first. Non-destructive is the goal, not a guarantee.
If BitLocker is on, have your recovery key ready (see how to find your BitLocker recovery key) and suspend protection before converting, as Microsoft’s documentation advises.
Open Command Prompt as administrator and validate first:

mbr2gpt /validate /disk:0 /allowFullOS

If validation passes, convert:

mbr2gpt /convert /disk:0 /allowFullOS

Restart, enter your firmware setup, and switch the boot mode from Legacy/CSM to UEFI. If you skip this step, the PC won’t boot from the converted disk.

Replace 0 with the right disk number from list disk. MBR2GPT has requirements (for example, no more than three primary partitions and no extended partitions), and /validate will tell you if your disk doesn’t qualify.

The destructive way: Disk Management and diskpart

Warning: converting with Disk Management or diskpart’s convert gpt command requires deleting every partition on the disk first. Everything on the disk is erased.

In Disk Management, “Convert to GPT Disk” is grayed out until the disk is empty. In diskpart, convert gpt fails on a disk with partitions, and the usual tutorials have you run clean first, which wipes the partition table. That’s fine for a brand-new or truly empty drive. On a drive with data on it, don’t do it unless everything is backed up and verified.

MBR vs GPT for data recovery

The partition style affects what happens when something goes wrong.

GPT’s backup header helps

Because GPT stores a second copy of its header and partition table at the end of the disk, damage to the start of the disk, from a bad sector, malware, or a tool writing to the wrong place, is often survivable. Recovery software and labs can read the backup copy and rebuild the primary one. With MBR, there’s just one table in one sector. If it’s damaged, the partitions have to be found by scanning the disk for file system signatures. That’s often possible, but slower and less certain.

Wrong conversions and “initialize” are common causes of data loss

Most partition-table disasters aren’t hardware failures. They’re someone clicking the wrong thing:

Running clean or deleting partitions to “convert” a disk that still had data on it.
Clicking “Initialize Disk” when Windows shows a drive as unknown or not initialized. Initializing writes a brand-new, empty partition table. If you’ve seen that prompt, read disk unknown, not initialized before you click anything.
Converting the wrong disk, because disk numbers in diskpart don’t always match what you expect.

The good news: these actions usually rewrite only the partition table, not the data behind it. If you stop immediately and don’t create new partitions or copy files onto the disk, the old partitions can often be found and restored. Our guide to partition recovery on an unallocated drive walks through it. What makes recovery much harder is continuing to use the disk: formatting the new partition, installing Windows on it, or running a full format.

The bottom line

GPT is the modern standard: it supports huge drives and 128 partitions, works with UEFI, and keeps a checksummed backup of its partition table at the end of the disk. MBR is limited to 2 TB and four primary partitions and is only worth using for old BIOS systems. To convert a Windows system disk, use MBR2GPT after a backup; Disk Management and diskpart’s convert gpt erase the disk. If a drive suddenly shows as unallocated or not initialized, stop before clicking anything.

If a partition table change has wiped out access to your files, or the drive itself is failing, our hard drive recovery service can help. It’s one flat $1,200 price for single devices, with free prepaid shipping, and you pay nothing unless the recovery succeeds.