FIELD GUIDESource-led reference

P080 / General / Guide

Gigabits, gigabytes and transfer-time estimates

Keep the units exact and the throughput assumption visible.

The useful distinction

Use GB for decimal file size and GiB for binary file size. Record whether a rate is bits or bytes per second.

Claim inspection dates: 2026-10-01 · Independent review pending

Guide note · not an individual product specification

The useful distinction

Understand the requirement.

NIST defines a byte as eight bits, a gigabyte as 1,000,000,000 bytes and a gibibyte as 1,073,741,824 bytes. A nominal gigabit-per-second link figure is not a measured file-transfer speed. [C080A]

Bounded facts, visible unknowns

Specifications and limits

Gigabits, gigabytes and transfer-time estimates facts and limitations
1 byte8 bits [C080A]
1 GB1,000,000,000 bytes [C080A]
1 GiB1,073,741,824 bytes [C080A]
Verified device listNot included. Check exact device and accessory documentation.
A boundary, not an omission to guess around.

No benchmark, negotiated USB mode, hardware support or actual completion-time guarantee is supplied.

Before you connect

What to check

  1. Choose the correct file-size unit.
  2. Enter a documented nominal rate or an explicit hypothetical rate.
  3. Label the usable fraction as an assumption, not a benchmark.
  4. Keep disk, workload, thermal and protocol constraints visible.
Trace a supported connection class →

A transparent example

A decimal 10 GB file over an ideal 10 Gbit/s link takes 8 seconds by arithmetic. A user-assumed 80% usable fraction changes that scenario to 10 seconds, without claiming that 80% is typical.

Your next step

Move from the form to the requirement.

The source trail

Evidence for this page

AI-assisted inspection is not independent engineering review. Source scope and access limitations are disclosed below. Procedural checklists are editorial requirements, not hardware measurements.

C080ASource checked · pending review

NIST defines a byte as eight bits, a gigabyte as 1,000,000,000 bytes and a gibibyte as 1,073,741,824 bytes. A nominal gigabit-per-second link figure is not a measured file-transfer speed.

NIST · Definitions of the SI units: the binary prefixes ↗

Locator: Examples and comparisons with SI prefixes
Access: public page. Byte/bit and decimal/binary unit definitions only; transfer worksheet formula is original arithmetic.

S054: full source recordInspect review dependencies → (private workspace)

Claim scope: Named standard or manufacturer description only; procedural checks are editorial recommendations, not hardware tests.. Next review due 2026-12-30.

Suggest a correction to this field note →

Evidence behind this page

Scope first. Source second. Approval separate.

1 linked sources · 1 scoped claims · 0 sources with inspection/access flags.

Page scope: consumer_pilot

Assessment 2026-10-22 · earliest scheduled source review 2026-12-30. This is a recorded-date assessment, not a live source check. Page-level independent review is not established by this panel.

Inspect 1 source scopes, access limits and dates

S054 · Definitions of the SI units: the binary prefixes

NIST · Public-institution domain · inspected 2026-10-01 · due 2026-12-30

Within inspection window

Scoped support: Byte/bit and decimal/binary unit definitions only; transfer worksheet formula is original arithmetic.

Not established / limitations: Byte/bit and decimal/binary unit definitions only; transfer worksheet formula is original arithmetic.

Locator: Examples and comparisons with SI prefixes

Trace 1 claims to their source records

C080A · P080

NIST defines a byte as eight bits, a gigabyte as 1,000,000,000 bytes and a gibibyte as 1,073,741,824 bytes. A nominal gigabit-per-second link figure is not a measured file-transfer speed.

Claim scope: Named standard or manufacturer description only; procedural checks are editorial recommendations, not hardware tests.

Source links: S054 · Evidence trail → (private workspace)

Prepare this page for review → (private workspace)Read the evidence method →

Recorded evidence only. An inspection date, publisher label, source link or generated packet is not independent technical review, hardware testing, fabrication approval or a compatibility verdict.