GB to TB Converter

This conversion translates a gigabyte value into terabytes using a fixed 1,024 divisor. One gigabyte is 1,024 megabytes, and one terabyte is 1,024 gigabytes. That fixed ratio applies whatever number gets entered.

This differs from a decimal-based (1,000-per-step) reading that most drive and cloud-storage marketing uses. JEDEC's JESD100B.01 standard historically applied decimal SI prefixes to computer memory. That history is part of why decimal figures show up so often on storage packaging. Operating systems, by contrast, report free space using the binary convention this page uses.

IEC 80000-13:2008 formalizes that binary convention, naming 1,024 gigabytes a tebibyte (TiB) to distinguish it from the decimal terabyte. This page's GB and TB labels follow that same 1,024 basis, even though the interface keeps the familiar names. The gap between the two conventions is close to 10% at this exact pair, the point where it becomes hard to ignore. NAS and RAID management consoles typically report array capacity in this same binary TB. That's one reason a "10TB" array often shows as a smaller usable figure once formatted.

Divide the gigabyte value by 1,024 to get the equivalent in terabytes. The formula is TB = GB ÷ 1,024, applied the same way for every input on this page.

It's plain integer division rather than an approximation, holding steady no matter how large the GB figure is. The reverse move, multiplying a TB value by 1,024, is exactly what the swap control does behind the scenes.

These examples use realistic drive and cloud-storage sizes rather than abstract numbers. That is the scale most people search this specific pair for.

1,024 GB converts to exactly 1 TB, confirming the baseline every other value here scales from. A 500 GB laptop SSD, a common budget configuration, converts to about 0.488 TB. A drive marketed as "2TB" is usually 2,000 GB in the manufacturer's decimal convention. That converts to about 1.953 TB here, not an even 2. Decimal inputs work the same way: 1,536.5 GB converts to about 1.501 TB. A 4-bay NAS array showing 8,000 GB of raw capacity converts to roughly 7.813 TB before accounting for any RAID overhead.

Dividing by 1,024 in code produces the same result as this converter, since both use integer powers of 1,024 rather than floating-point approximations. This comes up whenever an app needs to display a drive's free space or a cloud quota in TB instead of GB.

These functions return the identical figure this page shows, since both use the 1,024 divisor. For TB-to-GB, multiply by 1,024 instead, the operation the swap control triggers on this page. Save rounding, such as `toFixed(2)`, for the last step, not before feeding the result into another calculation.

A multi-GB backup archive grows by roughly a third once it's Base64-encoded for transfer. ToolkitWizard's Base64 Encoder shows exactly how much that adds at GB or TB scale. A SHA-256 digest of that same archive is still just 32 bytes, GB or TB alike. ToolkitWizard's Hash Generator proves that fixed length in one click.

function gbToTb(gb) {
  return gb / 1024;
}
// gbToTb(2000) -> 1.953125

def gb_to_tb(gb):
    return gb / 1024
# gb_to_tb(2000) -> 1.953125

The GB-to-TB divisor of 1,024 runs through integer division. Results stay exact across the full range this converter handles, TB-to-GB included by way of swap.

A gigabyte value stays entirely within the browser tab where it was entered. ToolkitWizard has no server route this calculator calls, in either direction.

No cookie or analytics event ties back to a specific value converted here, consistent with every other measurement tool ToolkitWizard runs. The entered figure vanishes the instant the page reloads or closes.

The most common mistake on this pair is treating a manufacturer's decimal TB figure as identical to this converter's binary TB. A "10TB" external drive is 10,000 GB in decimal terms, but converts to only about 9.31 TB here, a gap of roughly 7%. A second mistake is confusing gigabyte (GB) with gigabit (Gb). The capital B versus lowercase b changes the value by a factor of eight.

Comparing a purchased drive's advertised capacity against what the operating system reports after formatting stacks both mistakes on top of each other. Formatting overhead trims additional space beyond the unit-convention gap covered above. Neither loss points to a faulty drive or storage that has genuinely gone missing.

A fourth mistake is folding RAID overhead into the same explanation as the decimal-versus-binary gap. A RAID array reserves capacity for parity or mirroring on top of the unit-convention difference already covered here. The usable TB figure can end up well below both the marketed and the binary-converted numbers as a result. Stating the RAID level alongside any usable-TB figure keeps that comparison honest across two arrays that share the same raw capacity on paper.

This table covers common GB values, from a small SSD up to multi-drive NAS capacities. Each figure is computed with the same 1,024 divisor used throughout this page.

Figures under 1 TB round to three decimal places, close enough for everyday drive-capacity comparisons. A value not shown here is better run through the calculator above than estimated between two rows.

This page is the dedicated home for GB-to-TB, and for TB-to-GB through swap. It has more room for worked examples and FAQs than the all-units hub can spare for one pair. Figures checked here match the hub exactly, since both share the same 1,024-byte basis.

Each other high-volume pair on this cluster gets that same dedicated treatment, linked below rather than squeezed into this page. That keeps every converter narrowly aimed at the one conversion its own visitors searched for.