"How Much Data Will a 4G Solar Camera Use Per Month?" — The Answer Distributors Should Give Buyers

The number first: 1–3 GB per camera per month

For one 4G solar camera watching a compound, plan on 1–3 GB of mobile data per month — in most markets, the cheapest prepaid bundle a carrier sells. A camera nobody actively watches, recording locally and only pushing alerts, can finish the month under 1 GB. A camera that someone opens on their phone for an hour a day will use 8–14 GB. The top-up is decided almost entirely by how often a human opens the live view, not by the camera being switched on 24 hours a day.

That surprises most first-time buyers, and it is the single most useful thing a distributor can explain during a sale. The fear that a 24/7 camera means a 24/7 data bill kills deals that should close. It is also the fear that pushes a buyer toward a cheaper PIR-triggered unit that misses half of what walks across the yard.

Why the bill is small: the SIM is for viewing, not for recording

On an AOV (Always-On Video) camera, continuous recording is written to the microSD card inside the housing — up to 128 GB on our models — at zero data cost. AOV is an industry-generic design, not a proprietary feature: the camera keeps the sensor running at low standby power and uses on-device AI scene analysis to decide what matters, instead of waking on a PIR trip and missing slow movement or anything outside the sensor's wedge.

The SIM only carries four things:

• the live stream, while someone is actually watching it;
• short event clips and notification thumbnails;
• a keep-alive/status heartbeat and time sync;
• occasional firmware updates.

Nothing else crosses the network unless the customer deliberately enables continuous cloud upload, which is the one setting that turns a 2 GB month into an unbounded one.

Where the megabytes actually go

Bitrate depends on the encoder profile, scene complexity and how the installer leaves the stream configured, so treat 1 Mbps as a planning figure and confirm it against the unit in front of you before you put it in a quotation.

Run that arithmetic out to a month and the picture is clear:

The critical detail for anyone quoting a compound: data scales with viewers, not with cameras. Two family members watching the same camera for ten minutes each consume twice the data of one person watching for ten minutes. A site manager who leaves the app open on a desk all afternoon is the single biggest cost driver on any installation.

A worked example for a compound

Six cameras around a perimeter, each with its own SIM, one caretaker who checks each camera for about two minutes a day and receives roughly ten motion alerts per camera per day:

• Live view: 2 minutes/day on the sub-stream ≈ 4.6 MB/day ≈ 140 MB/month
• Event clips: 10 × ~1.5 MB ≈ 15 MB/day ≈ 450 MB/month
• Heartbeat and overhead: well under 100 MB/month

That is roughly 0.7 GB per SIM per month — comfortably inside the smallest bundle on sale, on every one of the six lines. The customer's real monthly exposure is six small top-ups, not one large one. When a client insists on a single number for a proposal, 2 GB per camera gives you headroom for a bad month without overselling.

Where a carrier offers pooled M2M or multi-SIM data, take it. Quiet cameras subsidise the one camera on the gate that everybody watches, and you stop fielding calls about a single SIM running dry mid-month.

Settings that decide whether a client pays for 1 GB or 10 GB

Commission the site properly and the running cost looks after itself. Physical installation takes 5–10 minutes per camera; the configuration decisions below take about as long and matter more to the customer's monthly bill:

• Default the mobile app to the sub-stream. Most users never notice on a phone screen, and it cuts live-view data by roughly two thirds.
• Cap event clip length. Ten seconds is enough to identify a person. Thirty seconds triples the notification cost for no additional information.
• Use AI filtering — person and vehicle — rather than raw motion. Fewer false alerts from branches, rain and livestock means fewer clips crossing the network, and fewer alerts the customer learns to ignore.
• Leave continuous cloud upload off unless the customer has specifically bought and understood it.
• Set the microSD card to overwrite. Local recording is what keeps the network out of the recording path in the first place.

One more thing worth saying to buyers: heavy live streaming costs battery as well as data. On a site where people genuinely watch a lot, or where the rainy season cuts panel yield, quote the higher-capacity hardware rather than explaining flat batteries later.

What this means for your purchase order

Our 49 AOV SKUs, all IP66, sit in four series:

These sit inside a 150-SKU catalogue; the full range is on our product pages. Two points connect this table to the data question. First, a dual- or triple-lens unit can serve more than one view, so a customer watching every channel at once uses proportionally more data than the single-sensor arithmetic above — worth stating explicitly when you quote the SG-D42G or SG-S43G series. Second, the 20000mAh / 15W SG-D42G-15F66 series is the one to specify for sites with heavy remote viewing or poor winter sun, because streaming draws power the panel has to replace.

Resolution is 1080p–2K as standard across the range; 4K is available only as a custom or OEM build. Cameras are built by Shenzhen Leksell, established 2012, TÜV Rheinland certified with CE, FCC and RoHS.

Quoting the running cost is part of the sale

A trial order starts at MOQ 10; OEM and private label — available on all models, including all 49 AOV SKUs — starts at 100 units. Samples ship in 7–10 days by air, bulk in 25–40 days by sea, and stock held by our Ho Chi Minh City office reaches Vietnamese customers in 7–10 business days. Terms and current wholesale pricing are set per order; margins run 20% from around 10 units and 30% from around 50, with the structure set out on our dealer page.

If you are building a spec sheet for your own market, put a data line on it: expected monthly usage at the default settings, the recommended bundle size, and the one setting (cloud upload) that changes the answer. Distributors who publish that number close faster than those who let the customer guess — and they get fewer support calls in month two.