GParted Live: The Complete Partitioning Guide

GParted (GNOME Partition Editor) is the de facto standard free tool for creating, resizing, moving, and repairing disk partitions on Linux and beyond. GParted Live packages it as a small, bootable Debian-based Linux distribution, which matters enormously for one reason: you can’t safely resize or modify a partition that’s actively mounted and in use by a running operating system. Booting from external media sidesteps that problem entirely by running GParted outside of any OS installed on the disk you’re working on.

This guide is built to be used two ways: read start to finish for a full working understanding, or jump straight to the section matching your task.

1. Creating and Booting GParted Live

Getting the ISO

Download the current GParted Live ISO from the official source at gparted.org/download.php, which redirects to SourceForge for the actual file. As of early 2026 the current stable release is the 1.8.x line (built on a current Debian base) — always grab the current release rather than an old cached ISO, since newer releases include updated file system drivers (particularly important for newer Btrfs, exFAT, and NTFS features) and kernel-level hardware support for recent SSDs and NVMe controllers.

Verify the download. GParted’s download page publishes checksums (and often GPG signatures) for each release. For a tool that’s about to modify your disk partition tables, confirming you have an unmodified, official image is not optional paranoia it’s a five-second check worth doing every time:

sha256sum gparted-live-*.iso
# compare against the published checksum on gparted.org

Creating Bootable USB Media

On Linux, the simplest reliable method is dd, used carefully:

# Identify your USB device FIRST — get this wrong and you will overwrite the wrong disk
lsblk

# Write the ISO (replace /dev/sdX with your actual USB device — NOT a partition like /dev/sdX1)
sudo dd if=gparted-live-1.8.1-3-amd64.iso of=/dev/sdX bs=4M status=progress conv=fsync

⚠️ Warning: dd overwrites the target device completely with no confirmation prompt. Double- and triple-check of=/dev/sdX points at your USB drive, not an internal disk. There is no undo.

If you’d rather avoid raw dd, Ventoy is a strong current alternative: install Ventoy once to a USB drive, then simply copy ISO files (GParted Live and others) onto it Ventoy handles making them bootable, and you can carry multiple bootable ISOs on one drive without re-flashing each time you switch tools.

On Windows, use Rufus (the long-standing community-preferred tool for this): select the ISO, select your USB drive, leave partition scheme on the Rufus default (GPT for UEFI systems, MBR for legacy BIOS Rufus generally detects the right one automatically based on your system), and write. Rufus will warn you that the target drive’s contents will be erased confirm only once you’ve verified the correct drive letter.

On macOS, dd works the same way as Linux (device paths look like /dev/diskN use diskutil list to identify the right one, and make sure to write to the raw disk device /dev/rdiskN for meaningfully faster writes), or use a GUI tool like balenaEtcher if you prefer a safer, guided UI with device-selection confirmation built in.

Read more about GParted Live 1.8 Released With Linux Kernel 6.18

Burning to CD/DVD

Less common today, but if optical media is your only option, burn the ISO as a disk image (not as a data file) using your OS’s built-in “burn disc image” function or a tool like cdrecord/wodim on Linux, Disk Utility on macOS, or the built-in Windows ISO burner.

Booting the Media

1. Insert the USB/CD and reboot the target machine.
2. Enter the boot menu or firmware setup (commonly F12, F11, Esc, or Del depending on manufacturer — check your system’s boot screen or manual).
3. Select the GParted Live media as the boot device. On UEFI systems, make sure you’re selecting the UEFI boot entry for the USB drive if you intend to work with GPT-partitioned UEFI-booted disks — booting in legacy/BIOS-compatibility mode on a UEFI target system can cause confusing partition table or boot flag issues later.
4. GParted Live will present a boot menu with keyboard, language, and screen resolution prompts (you can generally accept defaults by pressing Enter through each), followed by a choice between several boot modes — normal graphical mode is the default and correct choice for most users. If graphics fail to initialize, a “Safe graphics settings” / vga-normal fallback mode is available specifically for problematic GPUs or virtual machines (see Troubleshooting).

What to Expect on First Launch

GParted Live boots directly into the GParted application window on a minimal desktop — there’s no separate desktop environment to navigate through first. On launch, GParted automatically scans all connected disks and displays the first detected disk’s partition layout. If you have multiple disks connected, you’ll select between them via a dropdown in the top-right of the toolbar (covered next).

2. Interface Navigation

Layout Overview

The GParted window is organized around a few consistent regions:

• Menu bar (top): GParted, Edit, View, Device, Partition, and Help menus. Most actions are also available via toolbar icons or right-click context menus, so you rarely need to dig through menus once you’re familiar with the icons.
• Toolbar (below the menu bar): icons for New, Delete, Resize/Move, Copy, Paste, Undo, Apply (the green checkmark), plus the disk selector dropdown on the right showing the currently active disk (e.g., /dev/sda) and its total size.
• Graphical partition map (main upper pane): a proportionally-sized visual bar representing the selected disk, with each partition drawn as a segment sized relative to its actual capacity, color-coded by file system type. Unallocated space appears as a distinct gray/hatched segment.
• Partition list/table (lower pane): a row-per-partition table with columns for Partition (device name, e.g., /dev/sda1), File System, Label, Size, Used, Unused, and Flags.
• Operations queue / pending operations pane: appears at the bottom once you’ve staged at least one change, listing every queued operation in order before you apply anything (see Section 4).

Reading Partition Information

• Partition name — the device path (e.g., /dev/sda1). On Linux, sdX denotes SATA/SCSI/USB disks in enumeration order, nvmeXnY denotes NVMe disks, and the trailing number is the partition index.
• File system — the format applied to that partition (ext4, NTFS, FAT32, Btrfs, XFS, etc.). A partition can also show as unknown or unallocated if it lacks a recognized file system or hasn’t been formatted at all.
• Size / Used / Unused — total partition capacity, and (when GParted can read the file system) how much of that capacity currently holds data versus how much is free within the partition itself. This is distinct from unallocated disk space outside any partition.
• Flags — partition-table-level markers, most commonly boot (marks the active/bootable partition on MBR disks), esp (EFI System Partition, required for UEFI booting on GPT disks), lvm, raid, swap, and hidden. Flags are set via Partition > Manage Flags.
• Status/color coding — unmounted partitions are typically shown in a lighter shade; mounted/in-use partitions are marked distinctly (often with a small lock-like or highlighted indicator) since GParted restricts certain operations on partitions that are currently mounted.

Key Terminology (first use)

• Partition table — the master index at the start of a disk recording where each partition begins and ends. The two schemes you’ll encounter are MBR (older, max 4 primary partitions without extended/logical partitions, disks up to 2TB) and GPT (modern standard, effectively unlimited partitions, required for disks over 2TB and for UEFI booting).
• File system — the format that organizes how data is stored within a partition (ext4, NTFS, FAT32, Btrfs, XFS, etc.) — distinct from the partition table, which organizes the disk as a whole.
• Allocation unit / cluster size — the smallest block of disk space a file system will allocate to a file, even if the file is smaller. GParted generally handles this automatically per file system, but it’s exposed on Windows-side tools and worth knowing about if you’re troubleshooting unexpectedly high “used space” reports.
• Unallocated space — disk capacity not currently assigned to any partition. This is what you need available (either from unused disk space or freed up by shrinking an existing partition) before creating a new partition.

Selecting the Right Disk

Before doing anything else, confirm you’re looking at the correct disk in the top-right dropdown. This is the single most consequential navigation step in the entire tool — every operation you queue applies to whichever disk is currently selected, and GParted does not ask “are you sure this is the right disk” beyond the disk name and size shown in that dropdown. Cross-check the size shown (e.g., “500.11 GiB”) against what you know about your physical disks before proceeding.

3. Core Partitioning Tasks

Every task below follows the same underlying model: you stage the operation (it’s added to the pending queue and nothing on disk changes yet), then separately apply the queue (see Section 4) to actually execute it. This section covers staging; execution is covered next.

Creating New Partitions

When to use it: you have unallocated space (shown as gray/hatched in the graphical map) and want to carve out a new partition — for a new OS install, a dedicated data volume, a swap partition, etc.

Workflow:

1. Select the unallocated space segment in the graphical map (or the corresponding row in the partition list).
2. Click New in the toolbar (or Partition > New).
3. In the dialog, set:
   • Partition type — Primary, Extended, or Logical (only relevant on MBR disks; GPT disks don’t have this distinction and this option won’t appear).
   • File system — choose based on intended use (see guidance below).
   • Label (optional) — a human-readable name for the partition, supported by most modern file systems.
   • Size — drag the graphical slider or type an exact size in MiB. You can also set free space to leave before/after the new partition if you want a gap.
4. Click Add. This stages the operation — nothing is written to disk yet.

Choosing a file system:

• ext4 — the standard choice for Linux system and data partitions; mature, well-supported, good general performance.
• XFS — strong choice for large files and high-throughput workloads (common on servers); excellent at handling large partitions.
• Btrfs — modern Linux file system with built-in snapshots and checksumming; increasingly common as a root file system default (e.g., on openSUSE, Fedora options), but has a different mental model (subvolumes) worth understanding before relying on it for a system disk.
• NTFS — required if the partition needs to be read/written natively by Windows.
• FAT32 — maximum cross-platform compatibility (readable by nearly everything, including many embedded devices and UEFI firmware), but capped at 4GB per file — a real limitation for large file transfers.
• exFAT — a practical middle ground when you need both large-file support and broad cross-platform compatibility (external drives shared between Windows/macOS/Linux, for example).
• linux-swap — for a dedicated swap partition rather than a swap file.

Resizing Partitions

When to use it: you need to grow a partition into adjacent unallocated space, or shrink one to free up space for something else.

Workflow:

1. Select the partition to resize.
2. Click Resize/Move in the toolbar (or Partition > Resize/Move).
3. In the dialog, either drag the partition’s edge handles in the graphical bar, or type exact values into “New size,” “Free space preceding,” and “Free space following.”
4. Click Resize/Move to stage the change.

Growing (expanding) a partition:

• Safe and generally well-supported when there’s adjacent unallocated space immediately after the partition. If the free space is before the partition rather than after, GParted can still do it, but this becomes a move-and-resize operation (see below) rather than a pure resize, which takes meaningfully longer and carries more risk.
• Most modern file systems (ext4, NTFS, XFS, Btrfs) support online or offline growing without data loss when done correctly through GParted.

Shrinking a partition:

• ⚠️ Higher risk than growing. Shrinking requires the file system to first move any data occupying the space being removed, then the partition boundary itself is adjusted. This means:
  • The partition’s Used space must fit within your target new size — GParted will refuse to shrink below the amount of data currently stored, and shows you the minimum size it can shrink to based on current usage.
  • Always run a file system check first (see below) before shrinking — a partition with existing file system errors is more likely to have problems during a shrink operation.
  • Leave headroom. Shrinking a partition to the exact minimum GParted reports is not recommended — leave a reasonable buffer (a few percent of the partition size, or more for actively-used system partitions) rather than cutting it as close as the tool technically allows.

Deleting Partitions

⚠️ This is one of the operations flagged for irreversible data loss. Deleting a partition removes its entry from the partition table — the underlying data isn’t immediately wiped, but it becomes unallocated space that GParted (or anything else) may write over at any time, and without specialized recovery tools, the data is effectively gone the moment you delete and apply.

Workflow:

1. Select the partition.
2. Click Delete in the toolbar (or Partition > Delete).
3. The partition immediately shows as pending deletion in the queue it’s not yet applied.

Before deleting: confirm you’ve identified the correct partition (cross-check size, label, and file system type against what you expect), and confirm you have a backup of anything on it you might need. There is no “recycle bin” for this — once you delete and apply, recovery requires third-party data-recovery tools working against raw disk sectors, with no guarantee of success.

Moving Partitions

When to use it: you need to relocate a partition’s starting position on the disk — commonly to consolidate unallocated space in a specific location, or as a side effect of a resize operation involving preceding free space.

Workflow: handled through the same Resize/Move dialog described above adjusting “Free space preceding” effectively moves the partition’s start position.

⚠️ This is the slowest and highest-risk common operation. Moving a partition means physically rewriting every block of data to a new location on the disk, rather than just updating a boundary marker (unlike a pure resize into adjacent free space, which doesn’t need to relocate existing data). For a large, heavily-used partition, this can take a long time and represents extended exposure to interruption risk — a power loss or system crash mid-move is far more consequential than one mid-resize. Back up first, and ensure a stable, uninterruptible power source if working on a laptop or during a storm.

Formatting Partitions

When to use it: you want to apply a fresh file system to a partition — either a newly created one, or an existing one you’re repurposing (which erases its current contents).

Workflow:

1. Select the partition.
2. Go to Partition > Format to, and choose the target file system from the submenu.
3. This stages a format operation.

⚠️ Formatting an existing partition destroys its current data. There is no partial/selective formatting — it’s a full wipe of that partition’s file system and everything on it.

4. Applying Changes and Execution

The Staging Model

Every action described above create, resize, delete, move, format only stages an operation into the pending queue shown at the bottom of the GParted window. Nothing is written to disk until you explicitly apply the queue. This is GParted’s core safety mechanism: you can stage several operations, review them as a batch, remove or reorder ones you change your mind about (via Edit > Undo for the most recent staged operation, or by clearing individual queued operations), and only commit once you’re confident in the full plan.

Reviewing Before Applying

Before clicking Apply, review the operations queue carefully it lists each staged operation in plain language (e.g., “Shrink /dev/sda2 from 500.00 GiB to 300.00 GiB,” “Create new Ext4 partition #3”). This is your last checkpoint to catch a mistake a wrong disk selection, a wrong target size, an accidental delete before anything becomes real.

Applying the Queue

1. Click the green checkmark Apply icon in the toolbar (or Edit > Apply All Operations).
2. GParted shows a confirmation dialog summarizing the pending operations one final time — confirm to proceed.
3. A progress window opens, showing each operation executing in sequence with a progress bar and running log output. Operations execute in an order GParted determines is safe (not necessarily the order you queued them), and each operation shows a green checkmark on success or a red X on failure as it completes.

Verifying Changes Before Applying

Use the pending operations queue as your review checkpoint every time read each line item, confirm the disk device path matches your intended target, and confirm sizes are what you expect (watch for MiB vs. GB confusion, since GParted displays in GiB/MiB, which differ slightly from the GB/MB figures often quoted by drive manufacturers).

Mounted vs. Unmounted: What’s Actually Safe

• GParted itself will block or warn against most destructive operations on a mounted partition — this is a built-in safeguard, not something you need to remember to check manually. If a partition is mounted (including the GParted Live environment’s own working files, though that’s a separate live-boot filesystem, not your target disks), certain operations will be grayed out or will prompt you to unmount first.
• The safest practice regardless is to work entirely from GParted Live rather than a partition-editing GUI running inside your live production OS, precisely so the disk you’re modifying is never the one the running system depends on. This is the core reason GParted Live exists as a bootable environment rather than just a desktop application.
• Never attempt to resize or modify your system’s boot/root partition while booted into that same OS, even if a graphical tool nominally allows it — this is a reliable way to corrupt a running system. Boot into GParted Live for any operation touching your active OS’s partitions.
• Data partitions unrelated to the currently booted OS (a secondary internal drive, an external USB drive) can sometimes be safely unmounted and modified from within a running desktop environment using GParted or a similar tool but booting into GParted Live remains the more conservative, universally-safe approach, and is the only reliable option for a disk actively hosting the running OS.

Sources and Currency Notes

Version and release-cadence details (current 1.8.x stable line, release dates, changelog highlights like FAT/MSDOS LBA flag handling and file-system-signature erasure improvements) are drawn from GParted’s official news page (gparted.org) and current software-distribution listings, verified as of early-to-mid 2026. Core interface behavior, the stage-then-apply operational model, and file-system-specific resize/shrink mechanics have been stable across GParted releases for many years and are not expected to be version-sensitive for this guide’s purposes but always grab the current ISO from gparted.org before starting a real task, since file-system driver support (particularly for newer NTFS, Btrfs, and exFAT features) does meaningfully improve release over release.