IP Camera Bitrate Calculator: How to Set It

An IP camera bitrate calculator works out the data rate (in Mbps) and storage size (in GB) your security camera will produce, based on resolution, frame rate, compression, and recording time. You enter your camera’s settings and how long you want to keep footage, and it returns the bitrate you should set in the camera’s menu plus the total storage you’ll need. This guide explains the formula, how to use it, and common mistakes so you can size your network and hard drive correctly.

Formula

The core formula used by most IP camera bitrate calculators is:

Bitrate (Mbps) = Resolution factor × Frame rate (fps) × Compression factor

Where:

• Resolution factor – a number that represents the pixel count. For 1080p (1920×1080) it’s about 2, for 4MP (2560×1440) it’s about 4, for 4K (3840×2160) it’s about 8. These are relative to a baseline of 1 for 720p.
• Frame rate – how many frames per second the camera records (e.g., 15, 25, 30).
• Compression factor – a value that depends on the codec and quality setting. For H.264 at medium quality, a common factor is 0.07 (this yields roughly 2–4 Mbps for 1080p at 15 fps). For H.265, divide by about 2 (factor 0.035). For MJPEG, multiply by 10–20.

Then, to get storage:

Storage (GB) = Bitrate (Mbps) × 3600 × Hours per day ÷ 8 ÷ 1000

The 3600 converts seconds to hours, the ÷8 turns bits into bytes, and the ÷1000 converts megabytes to gigabytes (using decimal, not binary, which is what hard drive manufacturers use).

Worked Example

Using the default values from the calculator above:

• Resolution = 2 (1080p)
• Frame rate = 15 fps
• H.264 factor = 1 (this is a multiplier; the base 0.07 is already in the formula)
• Days = 7
• Hours per day = 24

Step 1: Bitrate = 2 × 15 × 1 × 0.07 = 2.1 Mbps

Step 2: Storage per day = (2.1 × 3600 × 24) ÷ 8 ÷ 1000 = 181,440 ÷ 8 ÷ 1000 = 22.68 GB/day

Step 3: Total storage = 22.68 × 7 = 158.76 GB

So for one 1080p camera recording 24/7 at 15 fps, you need about 2.1 Mbps of bandwidth and roughly 159 GB for a week of footage. The calculator above gives the same result (bitrate 2.1, storage per day 22.7, total 158.8).

Why Bitrate Matters

Bitrate is the single most important setting for IP camera storage and network planning. If you set it too low, video becomes blocky and details like license plates are unreadable. If you set it too high, you waste storage space and may saturate your network switch or Wi-Fi. The right bitrate balances image quality with practical limits.

For most surveillance scenarios, a bitrate between 2 and 8 Mbps per camera is typical. A 1080p camera at 15 fps with H.264 often needs 2–4 Mbps. A 4K camera at 30 fps may need 8–16 Mbps. These numbers change drastically with motion – a static scene compresses much better than a busy street.

How to Choose the Right Bitrate

Follow these steps to pick a bitrate for your camera:

1. Identify your camera’s resolution and codec. Check the spec sheet or the camera’s web interface. Common resolutions: 720p (1280×720), 1080p (1920×1080), 3MP (2048×1536), 4MP (2560×1440), 5MP (2592×1944), 4K (3840×2160).
2. Decide on frame rate. 15 fps is enough for most surveillance; 25–30 fps for fast motion (e.g., traffic).
3. Pick a codec. H.265 (HEVC) cuts bitrate roughly in half compared to H.264 at the same quality. H.264 is more compatible with older NVRs.
4. Use the calculator to get a starting bitrate. Then adjust based on the scene: increase by 20–30% if there’s constant motion, decrease if it’s a static hallway.
5. Check the camera’s maximum bitrate limit. Some cameras cap out at 8 or 16 Mbps. If your calculation exceeds that, lower the resolution or frame rate.

Common Mistakes and Misconceptions

Here are the most frequent errors people make when calculating bitrate:

• Mixing up bits and bytes. Bitrate is in megabits per second (Mbps), but storage is in megabytes or gigabytes. Remember: 1 byte = 8 bits, so 8 Mbps = 1 MB/s.
• Using binary vs decimal GB. Hard drives are sold in decimal GB (1 GB = 1,000,000,000 bytes), but operating systems often show binary GB (1 GiB = 1,073,741,824 bytes). The calculator uses decimal, which matches drive capacity labels.
• Assuming a constant bitrate. Many cameras use VBR (variable bitrate), which changes based on scene complexity. The calculated number is an average; actual bitrate may spike during motion.
• Forgetting audio. Audio adds a small amount (usually 8–16 kbps), which is negligible for storage but can add up over many cameras.
• Ignoring network overhead. IP streams have protocol overhead (Ethernet, IP, TCP/UDP), typically 5–10%. For planning, add 10% to your total bandwidth.

Bitrate vs. Resolution vs. Frame Rate

These three settings are interrelated, and changing one affects the others:

• Resolution – the number of pixels. Doubling resolution roughly doubles the bitrate for the same quality.
• Frame rate – how many images per second. Doubling the frame rate roughly doubles the bitrate, but with diminishing returns for motion smoothness.
• Compression – H.265 vs H.264 vs MJPEG. H.265 is the most efficient; MJPEG is the least (but simplest to decode).

A common misconception is that higher resolution always means better quality. In low light, a 2MP camera with a larger sensor can outperform a 4MP camera. Also, if your network can’t handle the bitrate, you’ll get dropped frames or lag, which defeats the purpose.

Storage and Bandwidth Planning

Once you have the bitrate, you can plan your storage and network:

• Storage: Multiply the bitrate by recording hours to get daily storage. For example, a 4MP camera at 6 Mbps recording 24/7 uses about 25.9 GB/day (6 × 3600 × 24 ÷ 8 ÷ 1000). Over 30 days, that’s 777 GB.
• Bandwidth: Add up the bitrates of all cameras. A 16-camera system at 4 Mbps each needs 64 Mbps of continuous bandwidth. Your switch and router must handle that, plus other traffic.
• Recording schedule: If you record only on motion, you can cut storage by 50–90%. Many NVRs support motion-triggered recording.
• Retention period: Decide how many days you need to keep footage (e.g., 7, 30, 90). Multiply daily storage by the number of days.

Frequently Asked Questions

Q: How many Mbps do I need for a 1080p camera?
A: For H.264 at 15 fps, a 1080p camera typically needs 2–4 Mbps. At 30 fps, 4–8 Mbps. With H.265, you can halve those numbers. The exact value depends on scene complexity and quality settings.

Q: What bitrate should I set for a 4K camera?
A: A 4K (3840×2160) camera at 15 fps with H.264 usually needs 8–12 Mbps. At 30 fps, 12–20 Mbps. With H.265, 6–10 Mbps. Start with these and adjust based on the image quality you see.

Q: Does frame rate affect bitrate linearly?
A: Roughly, yes. Doubling the frame rate from 15 to 30 fps will approximately double the bitrate, but the exact increase depends on the encoder. Some cameras use smart encoding that reduces bitrate for static scenes, so the relationship isn’t perfectly linear.

Q: How much storage do I need for 30 days of 4 cameras?
A: Use the calculator: for 4 cameras at 1080p, 15 fps, H.264, recording 24/7, each uses about 22.7 GB/day. Four cameras = 90.8 GB/day. Over 30 days, that’s 2,724 GB (2.7 TB). If you record only on motion, you might use 25–50% of that.

Q: Why does my camera’s bitrate vary even when I set it to constant?
A: Most cameras use VBR (variable bitrate) even when you set a target. The encoder adjusts to maintain quality, so bitrate spikes during motion and drops for static scenes. The number you set is an average, not a hard limit.

Q: Is H.265 always better than H.264?
A: H.265 (HEVC) provides about 50% better compression than H.264, so it uses less storage and bandwidth. However, it requires more processing power to decode, so older NVRs or viewers may not support it. Check your equipment before switching.

Limits of the Calculator

This calculator gives a good starting point, but it has limitations. It assumes average scene complexity and a standard encoder. Real-world bitrate can vary by ±30% depending on lighting, motion, and the camera’s firmware. For critical systems, always do a test recording and measure the actual bitrate from the camera’s status page. Also, the storage calculation uses decimal GB, so a 1 TB drive will show as about 931 GB in Windows. Plan for that difference.

Related

• Tree Benefits Calculator: Value Your Tree’s Impact
• Tee Calculator Optavia: How to Use It
• Tee Calculator for Athletes: Pace & Finish Time

in res | Resolution | - | 2 | 1
in fps | Frame rate | fps | 15 | 1
in h264 | H.264 bitrate factor | - | 1 | 0.5
in days | Days of recording | days | 7 | 1
in hours | Hours per day | h | 24 | 1
out bitrate | Bitrate | Mbps | res * fps * h264 * 0.07 | 1
out storage | Storage per day | GB | (bitrate * hours * 3600) / 8 / 1000 | 1
out total | Total storage | GB | storage * days | 1