Skip to main content
Camera FAQs

Camera Data Limit Reached: How to Optimize Camera Data Usage

Written By Philip Stanoev

Why You're Seeing This Alert

We show the alert when you reach your data limits. If your camera hits its monthly data limit, we notify you to help you stay informed about your usage. Once the limit is reached, automatic video features and streaming stop until the plan resets or is increased. Tracking and manual video requests keep working.

What stops working at the data limit

Once a camera reaches its monthly data limit, these stop until the plan resets or is increased:

  • Event (exception) media uploads, both video and snapshots

  • Live streaming

  • Historical streaming

  • Hyperlapse

  • Wi-Fi hotspot

  • Facial recognition picture upload (where enabled)

Usage is checked every 2 hours, so the limit may apply shortly after you cross it rather than at the exact moment. Data limits are applied only to cameras using a Zenduit-supplied SIM.

These keep working at the limit:

  • Tracking, meaning location and trip data

  • Manual video requests, so you can still pull footage of a specific incident

Manual video requests still use data, so request only the clips you need.

To restore video sooner, contact your account manager to increase the data plan (see Option A below). Otherwise video features come back automatically when usage resets at the start of the next calendar month.

Data Usage Is Not Pooled Across Devices

Each camera's data plan is independent. Cellular data overage billing is not pooled or aggregated across the devices on an account — a camera that stays under its limit does not offset one that goes over on a different device. Treat each camera's monthly data limit as its own separate limit when diagnosing an overage.

What Drives Your Camera's Data Usage

Your camera records to its SD card all the time, and that recording uses no data. Data is used only when something is sent over the cellular network. Two things decide how much:

  1. How often video is sent. Event video rules, hyperlapse frequency, live and historical streaming, hotspot and facial recognition. This is the biggest factor, and you control it in ZenduONE settings.

  2. How large each clip or stream is. Set by the resolution and frame rate (FPS) of each channel, and by how many channels are included. Raising resolution or FPS makes every upload larger.

Default settings: new cameras ship recording at 720p / 8 FPS per channel, with a 2 GB monthly data plan. Cameras used to send clips and streams at D1 / 4 FPS; they are now sent at 720p / 8 FPS, so each upload is larger than before for the same activity. These defaults often change after installation: many fleets raise resolution or frame rate on some channels, or ask their solution provider to do so. Any increase raises data usage on every clip and stream, so if your settings were changed from the default, or you add channels or enable video on many rules, review your plan size using the table below.

How Usage Figures Are Measured

Camera data-usage figures in the portal come from a once-daily batch pull from the camera backend, not a real-time feed. The pull cycles through all devices on the platform and does not run at a fixed time of day.

This means a camera installed only a few days ago may show little or no usage until the next pull completes — that's expected, not a sign the camera isn't working. If a customer questions a data-usage figure that looks stuck or missing, check how recently the camera was installed or reactivated before troubleshooting it as a fault.

Your Immediate Options

Option A: Quick Fix - Increase Your Data Plan

 Pros: Immediate resolutionCons: Increases monthly billing

Upgrade your data plan:

  1. Log into your account portal

  2. Go to "Assets" → "Edit Asset → Settings"

  3. Select affected device and choose new plan size

  4. Confirm - takes effect immediately

  5. Your camera resumes full functionality instantly

  6. Your next bill will reflect the prorated change

Note: If you are unable to do the above, connect with your solution provider to upgrade your plan. Plan changes are moving to your solution provider, so if you don't see the plan option in your account, contact them and they can change it for you.

Option B: Investigate and Optimize

Pros: No additional costs, often solves the issue permanentlyCons: Requires some configuration changes

Continue reading below for optimization steps →

Step 1: Investigate Why This Happened

See Where Your Data Is Going

Go to Assets → Data Usage and pick the date range (for example, Last month). Each camera shows its total usage and a breakdown by type.

  • Total Usage is the real usage reported by the SIM provider for cameras on a Zenduit-supplied SIM. Accuracy depends on the provider, shown next to each value.

  • All other columns are estimates reported by the camera. They are not exact and may not add up to the total. Use them to see which direction to look, then check the source below.

Column

What to check

Video Upload Usage

Exceptions page for rules set to upload video, and manual video requests made in the period

Snapshot Upload Usage

Hyperlapse interval, rules set to upload snapshots, and whether facial recognition is enabled

LiveStream Usage

Who has live streaming access and how long streams are left open. Limit access to key people and set a live stream timeout.

Historical Stream Usage

Who has historical streaming access. Limit it to key people.

Driver Calling Usage

Calls made through the camera

Others (GPS, Alarms, BLE)

Tracking and alarm data. This is expected and usually small.

Check Your Usage Pattern

Ask yourself:

  • Has someone been viewing live streams frequently?

  • Did you recently add new users who might be streaming?

  • Were there unusual events triggering excessive recordings?

    • Check exceptions page for this current month and compare with previous months to see if there excessive rules being triggered

  • Is this the first time or does it happen monthly?

Firmware Updates Count Toward Data Usage

A camera's data usage can be driven mostly by a firmware update download, not by streaming or feature use. This is why a usage chart can show heavy consumption in a period with zero live-streaming or video-request activity.

Firmware files can be large, and some firmware versions require two separate update steps instead of one, which roughly doubles the data used for that update. If a spike in usage doesn't line up with streaming or video requests, check whether a firmware update went out to that device around the same time before treating it as unexplained usage.

Determine If This Is Normal for Your Operations

Signs you NEED more data:

  • Multiple locations require constant live monitoring

  • Business operations need near-constant live viewing

  • This happens every month despite optimizations

Signs this is a ONE-OFF issue:

  • Someone left live stream running accidentally

  • New employee unfamiliar with efficient monitoring

  • First time this has happened

Which Camera Features Use the Most Cellular Data

Ranked from highest to lowest cellular data consumption:

  1. Live streaming — the biggest draw by far.

  2. On-demand video requests.

  3. Hyperlapse — recording interval affects this; a 10-minute interval uses noticeably less data than a 1-minute interval.

  4. Exception-triggered recordings — how much this uses depends on how many exceptions are configured to record video and how often they trigger.

Items 3 and 4 can switch order depending on how many exceptions are set to record video and how frequently they fire. To reduce data usage, start with live-streaming habits and hyperlapse intervals before adjusting exception/rule video actions.

Step 2: Take Action Based on Your Findings

If This Is Normal Usage → Upgrade Your Plan

Choose a plan based on how often video leaves the camera:

How you use the camera

Suggested monthly plan

Light: events sent as snapshots, occasional short live views

1 GB

Standard: video on key events, hyperlapse, short daily live views

2 GB (default)

Heavy: video on most rules, frequent live or historical streaming, several people viewing

5 GB

Continuous: 24/7 live monitoring

Custom plan, contact your solution provider

Plan size depends mostly on how often video is sent, not on how many channels the camera has. Recording to the SD card does not use data. Higher resolution or FPS makes every uploaded clip and stream larger, so if your settings were raised from the default, move up one tier.

To upgrade, see "Option A" above or contact your solution provider.

If This Was a One-Off → Optimize Your Settings

Start with what is being sent. Switching event rules from video to snapshot, slowing hyperlapse and limiting live streaming (steps below) usually save the most. If your channels were raised above the default resolution or FPS, lowering them again, or using D1 / 4 FPS on channels where detail matters less such as a cargo or side view, makes every remaining upload smaller. Contact your solution provider to change resolution or FPS.

Changes You Can Make:

  1. Switch from Unlimited Streaming to Adaptive/Limited Streaming

    • Contact your solution provider to help with this update

  2. Turn Off Hotspot if it is enabled

    • Contact your solution provider to help with this update

  3. Decrease Hyperlapse Frequency if Set To 1 min Setting

    • Access asset's Trips

    • Select the 10 mins Hyperlapse option and confirm

  1. Update Video Rule Actions To Snapshots

    • Access Your Video Rules In Admin

    • Change From Video To Snapshot

    • For Example, Speeding Should Only Be Set For Notifications Without Any Media Action

  1. Educate Your Team

    • Don't leave live streams running in background

    • Use snapshots for routine checks

    • Only stream live when actively investigating

Best Practices to Avoid Future Limits

  1. Set Up Smart Monitoring

    • Use Hyperlapse & Exceptions for general surveillance

    • Reserve live streaming for active incidents

  2. Create User Guidelines

    • Train staff on efficient camera use

    • Assign live stream privileges only to key personnel

  3. Regular Maintenance

    • Remove unnecessary event triggers

Was this helpful?

Still need help? Ask the team