| MB result seems 2.4% or more different | The source may use binary IEC values labeled informally as decimal MB. | Confirm whether the source actually means MB or MiB and compare the exact byte values. |
| 1 TB drive appears smaller in Windows | The advertised size is decimal while the interface may calculate using binary units. | Convert 1 TB into GiB and also allow for filesystem and reserved-space overhead. |
| Mbps and MB/s do not match | A megabyte contains eight megabits. | Divide Mbps by eight to estimate decimal MB/s, then account for transfer overhead. |
| Converted result is zero | An output precision setting may round a small nonzero value down to zero. | Increase decimal places or use scientific notation to reveal the small value. |
| Huge byte number is hard to read | A large SI or IEC unit converted to bytes produces a long integer. | Enable scientific notation for presentation and retain exact bytes for technical records. |
| A value copied from a spreadsheet is rejected | The input may contain separators, units, special characters or locale-specific punctuation. | Remove nonnumeric characters, check the decimal separator and reenter a standard numeric value. |
| Scientific notation gives an unexpected output | The exponent or input unit may have been misread. | Confirm that 1e9 means one billion of the selected source units and inspect the formula. |
| GB to GiB is not one-to-one | GB uses 10⁹ bytes; GiB uses 2³⁰ bytes. | Choose the standard intentionally and verify against the every-unit list. |
| History is missing on another device | History and favorites are held in the browser rather than synchronized by default. | Save important results externally; do not expect local history to appear on other devices. |
| Saved favorites disappeared | Browser data, private browsing or a cleanup tool can clear local storage. | Star pairs again and keep a separate document for critical recurring conversions. |
| Download estimate is much too optimistic | The calculation may assume full nominal bandwidth without protocol or server constraints. | Measure sustained transfer rates and include network overhead and variation. |
| Upload takes longer than download | Many internet connections have asymmetric upstream and downstream bandwidth. | Use measured upload Mbps rather than the advertised download speed. |
| Transfer size and speed units were mixed | The input may use Mb while speed uses MB/s, or vice versa. | Convert both sides into bits and seconds or use clearly labeled equivalent units. |
| Storage planner total seems too small | File averages, backups, duplicate copies or growth allowance may be missing. | Recheck representative file sizes and add retention, redundancy and growth headroom. |
| Storage planner total seems too large | The same files, backup copies or compression assumptions may be counted twice. | Review each source category and distinguish logical sizes from replicated physical capacity. |
| Conversion table cannot be copied | Clipboard permissions or browser restrictions may block the copy action. | Use a permitted browser context, retry the copy control or select and copy visible text. |
| CSV export is not available | A particular batch or CSV workflow may belong to the Pro tier. | Review current plan permissions or copy the available table into a spreadsheet manually. |
| Bit and byte units look identical | Uppercase B and lowercase b can be difficult to distinguish in some fonts. | Read the full unit name in the selector and inspect the factor-of-eight relationship. |
| The wrong kilobyte appeared | The interface contains both decimal KB and binary KiB. | Search the full unit name and select the intended SI or IEC standard. |
| Rounding hides the original amount | Low displayed precision loses visible fractional detail. | Increase precision, use scientific notation and preserve original input with units. |
| Large file cannot fit on a drive | Advertised storage capacity is not always the same as formatted usable free space. | Check actual free bytes, filesystem limits and destination requirements. |
| Cloud bill does not match a conversion estimate | Cloud pricing involves more than stored bytes, including requests, replication and data transfer. | Use the converter only for quantities and calculate cost from the provider billing schedule. |
| Conversion direction is reversed | Source and destination selectors were swapped. | Check from/to labels and use the swap button to correct the direction. |
| A negative file size was entered | Negative storage quantities do not represent ordinary physical file size. | Enter a nonnegative amount for capacity planning; treat negative differences as a separate calculation. |