A drive needs a partition table and a filesystem before anything can be stored on it, and many arrive with neither. Some are supplied ready to use for one particular operating system, which is a different thing from being ready for yours.
A drive out of a box is a surface with nothing organising it. Two structures have to be written before an operating system can use it.
The two things being created
A partition table describes how the drive is divided. Two schemes are in ordinary use, and one of them has a size limit: the older scheme cannot address beyond a certain point, and any large modern drive needs the newer one. Operating systems generally choose correctly when initialising a drive, and this is the setting to check if a large drive appears smaller than it should.
A filesystem goes inside a partition and is what actually stores files. This is the choice that decides which machines can read the drive.
Choosing a filesystem
The question to answer first is: what has to read this drive?
One machine, one operating system. Use that system’s own native filesystem. It will be the fastest and the best supported, and it will handle permissions properly.
Moving between different systems. The cross-platform options each have a compromise — a file size limit on one, an absence of journalling on another, an additional driver required on a third. Pick knowing which compromise you are accepting.
A drive going into a network enclosure. Do not format it at all. The enclosure writes its own arrangement and will erase whatever it finds.
What formatting takes away
A filesystem writes structures of its own before it holds a single file, so the usable figure is a little below the capacity. That is a genuine reduction and it is small on a large drive.
It is not the reason the drive shows a smaller number than the box. That is the unit convention — makers count in decimal terms, many operating systems display in units of 1024 — and it is separate from formatting altogether.
A drive that came ready to use
External drives are frequently shipped with a partition and a filesystem already on them, chosen for whichever platform the maker expects. That is convenient if it matches your machine and a nuisance if it does not, and reformatting is entirely normal.
Some also ship with the maker’s own software on a small partition. Nothing is lost by removing it; nothing is gained by keeping it if you are not going to use it.
Before formatting anything at all
Check the drive letter or device name twice. Formatting the wrong drive is instantaneous, irreversible from the interface, and the most common way people lose files while doing something routine.
If the drive is not new, assume something on it matters until you have proved otherwise. And whatever ends up on the drive afterwards, remember that a single drive is one copy of everything on it — the second copy is a separate decision, on separate hardware.
The questions that come up before an order
Should I use a quick format or a full one?
A quick format writes the filesystem structures and leaves the rest alone; a full one also passes over the whole surface, which takes hours on a large drive and can surface a bad area before you trust data to it. For a new mechanical drive the longer option is a reasonable investment; for a solid-state drive it writes a great deal for little benefit.
Do drives going into a NAS need formatting first?
No — the enclosure does it. It will erase whatever is on them and write its own arrangement, which is why anything already on a drive has to be copied off before it goes in. The enclosure’s setup process states this, and it means what it says.
Last reviewed 10 September 2026