About this Radiology Bandwidth Calculator
Radiology workflows can create bursty network demand. This calculator estimates the bandwidth needed to move daily image volume within a selected upload or synchronization window.
Who this calculator is for
- Radiology IT teams planning PACS, VNA, or teleradiology links.
- Network engineers estimating image transfer capacity.
- Operations teams comparing daily and peak imaging loads.
When to use it
- Estimate bandwidth for a site sending studies to a central PACS.
- Plan nightly archive sync or migration windows.
- Check whether a clinic link can support expected imaging volume.
How to use this calculator
- Enter studies per day and average study size.
- Set the number of hours available for transfers.
- Apply peak multiplier and overhead assumptions.
- Review required Mbps, average Mbps, and daily data volume.
Key assumptions
- 1 GB is converted to 8192 megabits.
- Study volume is averaged across the selected transfer window before peak and overhead factors are applied.
- The result is an operational estimate and does not replace network engineering validation.
Accuracy and testing
Review formula sources, default test cases, assumptions, unit handling, rounding rules, and changelog for this calculator.
How this calculator works
Daily GB = Studies per day x Average study GB. Average Mbps = Daily GB x 8192 / Transfer window seconds. Required Mbps = Average Mbps x Peak multiplier x (1 + overhead percent).
Required Mbps = studies per day * average study GB * 8192 / transfer window seconds * peak multiplier * (1 + overhead percent / 100).
Inputs explained
Studies per day
Daily imaging volume that must traverse the network path.
Transfer window
The number of hours available to complete the daily transfer volume.
Peak multiplier
A planning factor for uneven arrival patterns or peak clinical hours.
Overhead percent
Extra bandwidth for protocol overhead, retransmits, metadata, and operational cushion.
Understanding your results
Required bandwidth is a planning target. Actual network design should also consider latency, quality of service, redundancy, security inspection, and competing traffic.
Example scenarios
Clinic PACS upload
300 studies per day at 0.35 GB over an 8-hour window requires about 30 Mbps before peak and overhead factors.
Key Features
- Instant Calculation
- Private & Secure
- Mobile Optimized
Tips & Best Practices
- Use measured modality and PACS logs for average study size where possible.
- Increase peak multiplier for sites that upload mostly during clinic hours.
- Model image transfer separately from EHR, voice, video, and general internet traffic.