The technical arithmetic that comes up constantly: converting between bits and bytes, working out whether a download will finish before you need it, checking whether a plan's bandwidth is enough, encoding data for transfer. These tools are precise, unit-aware, and they show the limits of each answer — because in this area the wrong unit is the whole mistake. Everything runs in your browser.
Bits, bytes, KB, MB, GB, TB and PB, including binary and decimal conventions.
Open →How long a transfer takes at any speed, with protocol overhead applied.
Open →Speed, data transfer and capacity, in Mbps, MB/s or Gbps.
Open →Binary, octal, decimal and hexadecimal, with bit representation.
Open →Encode or decode text and files to and from Base64.
Open →Hex, RGB and HSL, with the contrast ratio for accessibility.
Open →Resize and compress product images to marketplace requirements.
Open →Most people use a handful of technical calculations every week — converting units, checking a file's size, working out a percentage. This section puts them in one place, with the unit conversions and the practical limits made explicit.
No — 100 Mbps is 12.5 MB/s, because there are 8 bits in a byte. Internet providers quote Mbps while download tools show MB/s, and that factor of 8 accounts for most of the confusion about whether a connection is fast.
About 3 Mbps for 1080p and 7 Mbps for 4K, with a video call taking 1.2 Mbps at 720p and 2.5 Mbps at 1080p. A terabyte-per-month cloud backup is only 3 Mbps on average but competes with everything if it runs during working hours.
Peak contention, protocol overhead of 5–15%, latency and packet retransmission all consume capacity before a link is technically full. A plan sized at 100% tends to fail at exactly the busiest times.
Most connections are asymmetric, often by a factor of ten or more — a 1000/50 line is one gigabit down and 50 Mbps up. The upload figure governs video calls, cloud backups and publishing large files, so sizing on download alone is the standard mistake.