What if you could make surveillance video smaller and clearer at the same time?

That sounds counterintuitive.

Normally, when video bitrate is reduced, image quality begins to suffer. Fine details disappear, edges become less defined, and pixelation becomes more noticeable.

But in a recent TotalMedia comparison, we observed something different.

We compared a camera's own H.265 compressed stream against the same surveillance video processed using TotalMedia Aware AI Compression.

Both streams were:

• 1920×1080
• 20 fps
• H.265

But the results were noticeably different.

Camera Compression: ~505.36 kbps
Aware AI Compression: ~420.04 kbps

Aware produced a smaller video stream.

Yet when the images were compared, the Aware-compressed video also appeared sharper and cleaner in several detailed portions of the scene.

Less data.

Better visual clarity.

That is where smarter compression becomes interesting.

Camera Compression vs. Aware AI Compression

Camera-compressed H.265 stream — 1920×1080, 20 fps, approximately 505.36 kbps.

TotalMedia Aware AI Compression — 1920×1080, 20 fps, approximately 420.04 kbps.

Take a close look at both images.

Pay particular attention to:

• Rocks and landscaping
• Pavement and sidewalk texture
• Bushes and foliage
• Vehicle edges
• Tree trunks
• Dark and shadowed portions of the scene

The difference isn't simply the bitrate.

The camera-compressed image shows more visible blockiness, pixelation, and loss of fine detail in several areas.

The Aware-compressed image maintains cleaner edges and more defined textures—even while operating at a lower observed bitrate.

That's an important distinction.

The Camera Is Already Compressing the Video

This isn't a comparison between raw, uncompressed video and compressed video.

Both streams use H.265 compression.

The camera has already compressed its video before Aware enters the equation.

That's exactly why this comparison matters.

Most surveillance systems already rely on compressed camera streams. Organizations aren't storing enormous uncompressed video feeds—they're using H.264, H.265, and similar technologies to keep bandwidth and storage manageable.

The question is whether that compression can be made more efficient.

In this example, Aware reduced the observed stream from approximately 505.36 kbps to 420.04 kbps, while the resulting image appeared cleaner in multiple areas.

Same resolution.

Same frame rate.

Same codec.

Less data.

And stronger perceived visual clarity in this captured comparison.

Why Lower Bitrate Doesn't Have to Mean Worse Video

It's easy to assume:

Higher bitrate = higher quality.

But bitrate only tells you how much data is being used.

It doesn't tell you how efficiently that data represents the scene.

Imagine two files containing the same information.

One requires 10 MB.

The other requires 5 MB.

If both preserve the information you actually need, the larger file isn't automatically better—it is simply larger.

Video compression follows a similar principle.

A compression system has to decide which information should be preserved and which information can be reduced.

When compression becomes inefficient, you begin seeing familiar artifacts:

• Blocky textures
• Blurred edges
• Smearing
• Lost detail
• Pixelation
• Poor definition in complex areas

This becomes particularly noticeable in surveillance footage because scenes often contain enormous amounts of visual complexity.

Trees.

Grass.

Rocks.

Fences.

Vehicles.

Shadows.

Text.

People.

Constant movement.

Simply lowering a camera's bitrate can reduce bandwidth and storage, but eventually image quality can deteriorate.

That's why the goal shouldn't be:

Use the lowest bitrate possible.

The goal should be:

Use the least data necessary while preserving the visual information that matters.

That's what smarter compression is designed to accomplish.

Look at the Image, Not Just the Bitrate

The easiest way to understand the difference is to stop looking at the bitrate number for a moment and examine the actual footage.

The rocks are a good example.

Small objects with irregular shapes and textures are difficult to compress efficiently. In the camera-compressed image, some of that texture becomes less defined and more block-like.

The same applies to foliage.

Leaves, branches, shadows, and overlapping textures create an extremely complex area for a video encoder.

In the Aware-compressed image, several of these areas appear more naturally defined despite the smaller stream.

You can also examine edges around vehicles, the sidewalk, and darker portions of the scene.

The point isn't that lower bitrate automatically produces better video.

It doesn't.

The point is that:

More bitrate does not automatically produce better useful video either.

Compression efficiency matters.

Smaller Streams Become a Big Deal at Scale

An 85 kbps difference may not sound dramatic when looking at one camera.

But surveillance infrastructure rarely consists of one camera.

Video streams can run:

24 hours a day.

365 days a year.

Across hundreds or thousands of cameras.

Every bit generated by those cameras eventually has to be transmitted, stored, or both.

Using the observed rates from this comparison:

Camera Compression — ~505.36 kbps

Approximately:

• 5.46 GB per day
• 164 GB per 30 days
• ~2.0 TB per year

Aware AI Compression — ~420.04 kbps

Approximately:

• 4.54 GB per day
• 136 GB per 30 days
• ~1.66 TB per year

That's roughly:

28 GB Less Data Per Camera Every 30 Days

Now multiply that difference across a deployment.

100 cameras: ~2.8 TB less data every 30 days

1,000 cameras: ~28 TB less data every 30 days

And remember: this is based only on this particular observed comparison.

Depending on the camera, scene, configuration, source bitrate, and desired output, the reduction can be significantly larger.

These calculations are illustrative and assume continuous average bitrate. Actual bitrate and data usage vary with motion, lighting, scene complexity, camera configuration, audio, metadata, and other factors.

Why Not Just Lower the Camera Bitrate?

If lower bitrate saves storage, there's an obvious question:

Why not simply turn down the camera's bitrate?

Because reducing bitrate and improving compression efficiency are not the same thing.

Push the camera bitrate too low and you may begin sacrificing the exact information your surveillance system is supposed to capture.

Details can disappear.

Objects can become harder to distinguish.

Motion can introduce additional artifacts.

Complex areas can become heavily pixelated.

You may have created a smaller video file—but you've also made the video less useful.

That's a poor trade.

The objective is to reduce the amount of data required without unnecessarily sacrificing useful visual information.

Our comparison demonstrates why that distinction matters.

The camera was already producing an H.265 compressed stream at approximately 505.36 kbps.

Aware reduced that to approximately 420.04 kbps.

But rather than simply looking like a more heavily compressed version of the camera stream, the Aware output maintained strong detail and appeared cleaner in several areas of the captured scene.

That's the difference between simply compressing more and attempting to compress smarter.

The Real Cost Isn't Just File Size

Every extra bit of surveillance video affects infrastructure somewhere.

More video data can mean:

• More storage capacity
• More hard drives
• More storage servers
• More network traffic
• More cloud transfer
• Higher cellular data usage
• Shorter retention periods
• More frequent infrastructure upgrades

This becomes particularly important for deployments using constrained connections such as LTE, 5G, satellite, remote WAN, or other bandwidth-limited networks.

Reducing the amount of video data moving through that infrastructure can help organizations support more cameras and longer retention without continuously expanding the systems behind them.

And if that reduction can be achieved while maintaining strong visual quality, the economics become much more interesting.

What About Larger Compression Reductions?

The approximately 505 kbps vs. 420 kbps comparison shown here is one captured example.

It shouldn't be interpreted as the maximum reduction Aware can achieve.

Depending on the source stream, scene, camera configuration, and deployment requirements, TotalMedia Aware can reduce video data requirements by up to around 90%.

That can translate into dramatically lower storage and bandwidth requirements.

But there is an important reason we're showing this particular example.

The camera stream was already relatively small.

It was already H.265.

It was already compressed.

And Aware was still able to reduce the observed bitrate further while producing an image that appeared cleaner in multiple areas.

That demonstrates a broader point:

Compression isn't just about how small you can make the video.

It's about what the video looks like after you make it smaller.

Make the Video More Efficient Before Expanding the Infrastructure

When surveillance systems begin running out of capacity, the traditional response is often to add more infrastructure.

More storage.

More hard drives.

More bandwidth.

Larger cellular plans.

Additional servers.

Or organizations begin compromising the video itself by reducing bitrate, resolution, frame rate, or retention.

But there's another question worth asking first:

Can the existing video be made more efficient?

This is what TotalMedia Aware is built to address.

Aware works with existing surveillance video infrastructure to reduce the amount of data required for video transmission and storage.

That can help organizations:

• Reduce storage requirements
• Reduce bandwidth consumption
• Extend video retention
• Lower cellular data usage
• Support more cameras on existing infrastructure
• Reduce cloud and data-transfer requirements
• Delay storage and network expansion

And, as this captured comparison demonstrates, reducing data doesn't necessarily have to mean accepting a worse-looking image.

The Numbers Tell Only Half the Story

Here's the comparison again:

Camera Compression

Resolution: 1920×1080
Frame Rate: 20 fps
Codec: H.265
Observed Bitrate: ~505.36 kbps

Aware AI Compression

Resolution: 1920×1080
Frame Rate: 20 fps
Codec: H.265
Observed Bitrate: ~420.04 kbps

Aware used less data.

But that's only half of what makes this comparison interesting.

Look back at the images.

The lower-bitrate Aware stream still maintains strong detail while appearing sharper and cleaner in several portions of the scene where the camera-compressed stream shows more noticeable compression artifacts.

That's why bitrate alone isn't enough to evaluate surveillance video.

The better question is:

How Much Useful Visual Information Are You Getting From Every Bit?

Smaller Video. Sharper Detail. Smarter Compression.

Surveillance cameras already compress video.

The opportunity is to do it more efficiently.

Our captured comparison shows exactly why.

Camera Compression: ~505.36 kbps

Aware AI Compression: ~420.04 kbps

Both are 1920×1080.

Both are 20 fps.

Both use H.265.

But the Aware stream requires less data while appearing cleaner and sharper in multiple detailed areas of the captured scene.

That's what smarter compression can change.

Not simply:

How small can we make the video?

But:

How much useful video can we preserve with less data?

See What TotalMedia Aware Could Save Across Your Deployment

Before purchasing additional storage servers, expanding network capacity, increasing cellular plans, or lowering camera quality to control costs, consider another option:

Make the video itself more efficient.

TotalMedia Aware is designed to help organizations dramatically reduce surveillance video bandwidth and storage requirements while preserving the visual information their teams depend on.

Smaller video. Sharper detail. Smarter compression.

➡ Learn More About TotalMedia Aware

Related Resources

➡ The Hidden Cost of Surveillance Storage: How to Cut Storage Costs by Up to 90% See how smarter compression can reduce storage infrastructure, hard-drive purchases, installation costs, and long-term operating expenses.

➡ What Is Edge AI Detection and How Does It Work? Discover how Edge AI prioritizes meaningful events while reducing unnecessary video transmission and storage.

➡ VMS vs NVR: What's the Difference? Understand how Video Management Systems (VMS) and Network Video Recorders work together to build scalable, efficient surveillance deployments.