When Excel treats a value as text, the cell shows a small green triangle in the upper-left corner, and the entry sits left-aligned inside the cell instead of right-aligned like a real number. Any SUM, AVERAGE, or arithmetic formula treats that text cell as zero, so totals silently undercount without throwing a visible error. Text-stored numbers usually arrive through CSV imports, copy-paste from a web page, a leading apostrophe such as '123, or a column that Excel loaded as text by default. Excel provides reliable fixes for plain numeric entries, but the harder case is when the cell holds a compound value such as 1.5 GB, 2048 MB, or 500 KB. Stripping the unit suffix by hand is tedious, and Excel's generic text-to-number commands do not understand unit labels, so the converted number still sits in the wrong scale. The Data Storage Converter is built for exactly this second stage, giving the exact byte value behind any storage label so the cleaned-up number can be pasted back into the sheet as a real, formula-friendly value.
What "Numbers Stored as Text" Means in Excel
The green triangle is Excel's standard error indicator called "Number Stored as Text". Excel applies it whenever a cell contains characters that look like a number but the cell has been marked as Text formatting, or whenever an apostrophe was typed ahead of the digits. Cells flagged this way cannot be summed, multiplied, or compared as numbers because Excel still sees them as strings. The visible symptom is a formula that returns the wrong total or a sort that puts 9 ahead of 100. The hidden symptom is that an audit of the spreadsheet shows the offending column but no broken cell reference. For storage-size sheets, the same indicator fires whenever a cell reads something like 1.5 GB, 1024 MB, or 0.5 TB, because the unit suffix blocks any automatic numeric interpretation. Confirming the issue is straightforward: click a flagged cell, look at the formula bar, and notice that the entry is left-aligned; if you type =ISNUMBER(A2) in a helper cell, it returns FALSE.
Quick Fixes Inside Excel for Plain Text Numbers
For numbers that have no unit suffix, three built-in methods work reliably and leave the value unchanged:
- Paste Special → Multiply by 1: type 1 in an empty cell, copy it, select the text-stored cells, then choose Home → Paste → Paste Special → Multiply. Multiplying each entry by 1 forces Excel to coerce it into a real number without changing the visible value.
- The VALUE() function: in a helper column, enter =VALUE(A2) and drag down. VALUE() converts a text string that looks like a number into an actual number; if A2 contains 1.5, VALUE returns 1.5 as a numeric result.
- Text to Columns: select the column, then go to Data → Text to Columns → Finish (with Delimited chosen but no delimiter boxes ticked). Excel rewrites every cell using its best numeric guess and the green triangles disappear.
These three methods each fail when the cell contains a storage label such as 1.5 GB or 2048 MB. VALUE() returns #VALUE!, Paste Special multiplies the whole text label by 1 and leaves the unit glued in place, and Text to Columns keeps the suffix attached. That gap is exactly where the Data Storage Converter fits, because it treats the unit suffix as a first-class input and returns the matching byte count.
When the Text Values Are Storage Sizes
Spreadsheets that compare disk capacities, cloud quotas, or backup windows usually contain compound strings like 1.5 GB, 2048 MB, or 0.5 TB. Each row has to be converted to a common unit, almost always bytes, before totals, averages, and side-by-side comparisons behave. A reliable workflow has three stages: separate the number from the unit (for example, split 1.5 GB into 1.5 and GB), look up the conversion factor for that unit in either the decimal (1000-based) or binary (1024-based) standard, and multiply so the rebuilt value lands in bytes. Stage two is where errors creep in. The same label — 1 GB — can mean 1,000,000,000 bytes (the way drive makers count) or 1,073,741,824 bytes (the way Windows reports it). Picking the wrong convention by hand introduces an off-by-a-few-percent error on every row, which multiplies into a misleading total at the bottom of the column.
| Unit | Decimal (SI) bytes | Binary (IEC) bytes |
|---|---|---|
| 1 KB / 1 KiB | 1,000 | 1,024 |
| 1 MB / 1 MiB | 1,000,000 | 1,048,576 |
| 1 GB / 1 GiB | 1,000,000,000 | 1,073,741,824 |
| 1 TB / 1 TiB | 1,000,000,000,000 | 1,099,511,627,776 |
| 1 PB / 1 PiB | 1,000,000,000,000,000 | 1,125,899,906,842,624 |
Convert Storage Labels With the Data Storage Converter
For each unique label that appears in your spreadsheet, the Data Storage Converter gives you the exact byte value in either convention so you can paste it back into Excel as a clean number. The tool runs entirely in your browser, so the values you enter never leave the device.
- Type the amount you want to convert into the storage value field.
- Pick the prefix standard — Decimal (1000) for drive makers, or Binary (1024) for what your operating system reports — then choose the source and target units.
- Read the converted result instantly, or tick 'Show all units at once' to see bits through petabytes together.
Worked example: a cell containing 1.5 GB. Enter 1.5, choose Decimal (1000), and set the source unit to gigabyte (GB) and the target to byte (B). The result is 1,500,000,000 bytes. Switch to Binary (1024) and the source to gibibyte (GiB); the result is 1,610,612,736 bytes. The decimal answer matches the drive label; the binary answer matches what Windows displays inside File Explorer. Paste 1500000000 into the Excel cell as a real number, then use a normal =SUM() formula on the column and the total will reflect every row correctly.
The same three-step flow handles every other label that can show up in the sheet — MB, TB, even the lowercase Mb for megabits when a network-speed column sits next to a file-size column.
Why a "1 TB" Cell Often Reads as 931 GB
The classic spreadsheet complaint in storage sheets is that a column labelled "drive size (TB)" contains values that look smaller than the marketing number. A row that should hold 1 reads as 0.909, or 0.895 depending on how the rounding was done. The reason is the unit-system mismatch in the table above, not a missing byte. A drive advertised as 1 TB is sold with the decimal definition: 1 TB = 1,000,000,000,000 bytes. Windows divides those same bytes by 1024 four times (B → KB → MB → GB → TB) and gets roughly 0.909 TB, but the column is still labelled "TB", so the displayed number shrinks even though no capacity has vanished. Per NIST's Prefixes for Binary Multiples and the IEC 80000-13:2008 standard, the correct binary unit for that number is the tebibyte (TiB), not the terabyte (TB), which is exactly the distinction the Data Storage Converter lets you toggle between. Re-labelling the column "Size (TiB)" and pasting 0.909 as a real number fixes the apparent loss without changing the underlying data.
Bits vs Bytes — The Speed Sheet Trap
The other common conversion error in storage spreadsheets is the bits-versus-bytes mix-up. Exactly 8 bits make 1 byte, in both the decimal and binary standards. Storage capacity is measured in bytes (uppercase B), while data-transfer and internet speeds are usually quoted in bits (lowercase b). A row that lists an internet link as 100 Mb/s is describing 100 megabits per second, which works out to about 12.5 megabytes per second (100 ÷ 8). A sheet that mixes the two units can overestimate download times by a factor of eight, which is the classic source of "why is my download slower than the plan" confusion. The Data Storage Converter includes bit alongside byte, so the same field can confirm both numbers: enter 100, choose Decimal, source megabit (Mb), target megabyte (MB), and the result is 12.5. Paste 12.5 into Excel and label the column MB/s so the unit and the value match.
| Context | Standard used | Example label |
|---|---|---|
| Drive / SSD advertised capacity | Decimal (SI), powers of 1000 | 1 TB = 1,000,000,000,000 B |
| Operating-system reported file size | Binary (IEC), powers of 1024 | 1 TiB = 1,099,511,627,776 B |
| Network transfer speeds | Decimal (SI), bits (lowercase b) | 1 Gb/s = 1,000,000,000 b/s |
| RAM and memory modules | Binary (IEC), historically | 1 GiB = 1,073,741,824 B |
The two conventions diverge further as the unit grows. By the time the spreadsheet reaches terabit-scale links, the gap between a 1 Tb cell (decimal, 10^12 bits) and a 1 Tib cell (binary, 2^40 bits) becomes too large to ignore. Cleaning the column once with the converter, pasting the converted values as plain numbers, and re-labelling each column with the exact unit it holds turns a misleading storage sheet into one where totals, averages, and forecasts all behave.