Your Cameras Are Recording. The Question Is Where — and Whether It Will Still Be There.

Almost nobody buys a camera system and then asks where the video goes. You buy it, someone mounts it, the app shows a live picture, and the job feels finished — the picture is proof the thing works. Months or years later something actually happens, you open the app looking for last Tuesday afternoon, and you find out what you really bought.

There are three common endings to that story and we have seen all of them. The footage was never being saved at all, only shown live. The footage was being saved to a box that is no longer in the house. Or the footage was being saved faithfully to a drive that quietly stopped working some time last spring, and nothing anywhere told you.

None of these are exotic failures and none of them are anyone being careless. They are all the same design problem wearing different clothes: a camera system is judged on the live picture, and the live picture keeps working long after the recording has stopped. This is a guide to finding out what you have before the day you need it, and it ends with a test that takes about ten minutes.

There are only three places footage can be

Strip away the brand names and every home camera writes its video to one of three places, or to some combination of them.

A card inside the camera. A microSD card in the camera body itself. Cheap, self-contained, and it keeps recording whether or not your internet is up — but it is a small card in a plastic box on the outside of your house, which is the least protected place in the entire system.

A recorder in the building. An NVR (network video recorder) or a hub — the box the cameras are wired or paired to, usually with a hard drive inside. This is what most multi-camera systems use, and it is where the most footage lives. Reolink, to take one vendor with clear public documentation, describes its NVR and Home Hub as local storage devices supporting large local storage options, and lists a camera microSD card, the NVR, a PC running its desktop client, an FTP server, or third-party software over RTSP/ONVIF as the places continuous recording can be sent.

Somebody else's servers. The cloud. Your camera uploads clips over your internet connection and you watch them back from an app. Usually a subscription, usually the least effort, and — this is the part that matters later — completely dependent on the upload actually happening at the moment of the event.

The first useful thing you can do today is find out which of the three you are on. Not which one you assumed, or which one you were sold. Most people who think they are "on the cloud" have a recorder in a closet, and a fair number of people who think they have recordings have a live view and nothing else.

The recorder is inside the building it is watching

Once you see this, you cannot unsee it, and it is the single structural weakness of local recording. The box holding all your evidence is sitting inside the thing the cameras are pointed at.

That is fine for the everyday jobs — a delivery dispute, a neighbour's dog, a fender-bender in the driveway, someone trying door handles at 3am. In all of those, the house is still standing and the recorder is still on its shelf, and local recording is genuinely excellent: it is fast, it is private, there is no subscription, and it does not care whether your internet is working.

It is not fine for the small set of events that take the building. A fire, a serious break-in, a flood in the room the box is in — those take the footage and the house in the same motion. The very incidents where footage would matter most are the ones most likely to remove it. That is not a flaw in any particular product; it is geometry.

We are deliberately not going to tell you how often burglars take recorders. You will find confident numbers on vendor blogs and forums and none of them are sourced to anything we would stand behind. The structural point does not need a statistic to be true: one copy, inside the building, is one copy inside the building.

The cloud camera stops being a cloud camera at the worst possible moment

The obvious answer to the paragraphs above is "put it in the cloud, then." And off-site copies genuinely do solve that problem — but cloud-only has a mirror-image weakness that is just as structural, and it is much less discussed.

A cloud camera has to upload. If your internet is down, there is nothing to upload to. The clip does not queue politely and arrive later unless the camera has its own local storage to hold it, which is exactly the thing a cloud-only camera does not have.

Now ask what tends to be happening during the events you care about. Power goes out and the router, the ONT and the cameras all go dark together. A storm takes the line down. Somebody deliberately kills the power. In each case the internet went away at the same instant the interesting thing started — and a cloud-only system's recording window closes precisely when it opens.

This is why we keep pointing customers at battery backup, and it is a much smaller purchase than people expect. A UPS on the router, the ONT or modem, and the recorder buys you the exact minutes that matter. We have written separately about which half of your internet setup fails in an outage and about what a UPS does that a surge strip does not; both are linked at the bottom.

Without a subscription, some cameras are a window, not a record

This is the one that surprises people most, so here it is in the vendor's own words rather than ours. Ring's support pages state plainly: "Without a subscription, you can view live video and respond to alerts as they happen." And on what the paid plan adds: "The only thing you don't get without a Ring Protect Plan is cloud video history and related recording features."

Read that carefully, because the wording is doing a lot of work. Live view works. Motion notifications work. Two-way talk works. The app is full of activity and looks completely healthy. What is not happening is the part you would only discover by going back and looking for something — the saving.

When there is a subscription, Ring says motion event videos "are stored in the cloud for up to 180 days from the recording date," which is a generous window. But the gap between "180 days of history" and "nothing at all" is a payment status, and payment status changes quietly: a card expires, a plan lapses after a house move, a subscription set up by an adult child stops renewing. Nothing about the live picture will tell you it happened.

We are not going to quote plan names or prices here. Ring's own pages disagreed with each other about the current tier names on the day we checked, and subscription pricing moves faster than any article can. Check it on the vendor's page, on the day, and check whether the plan is actually still active — that is the fact you need, and it takes a minute.

Retention is not a setting. It is a division problem.

People talk about their system "keeping 30 days" as if 30 days were a configured value. On a local recorder it usually is not. It is an outcome — the drive's capacity divided by how fast your cameras fill it — and it changes whenever anything on either side of that division changes.

Add two cameras to a four-camera system and you did not just add two camera feeds; you cut your history by roughly a third, because the same drive is now absorbing half again as much video per day. Turn a camera up from its default resolution to its highest, or switch one from motion-only to continuous recording, and you did the same thing. Nothing warns you. The installer who set it up quoted you a retention figure that was true about the system that existed that afternoon.

So do not try to compute it. There is an empirical answer sitting in your recorder right now that beats any arithmetic: open the playback timeline and scroll back to the oldest footage that still exists. That date is your real retention. If it is three days and you believed it was a month, you have just learned the single most important fact about your camera system, and it cost you thirty seconds.

It is worth re-checking that oldest-clip date any time the system changes — after a camera is added, after someone changes a quality setting, after a drive is replaced. It is the one number that summarises everything else.

The overwrite switch decides which way you lose

Every recorder eventually fills its drive, and there are only two things it can do about it. It can start overwriting the oldest footage, or it can stop recording. Which one your box does is a setting, and the two failure modes it produces are completely different.

Reolink's own troubleshooting documentation for an NVR that has stopped recording tells users to make sure the overwrite function is enabled so that, in its words, "when the HDD is full, the oldest footage is overwritten" — and it lists an HDD that "fails to overwrite older footage automatically" as one of the specific causes of a recorder that has stopped capturing.

That is the trap in miniature. With overwrite on, you have a rolling window and you lose the distant past — which is almost always the right trade. With overwrite off, the box fills up on some unremarkable Tuesday and then records nothing ever again, while the cameras stay online and the live view stays perfect. Every day after that Tuesday is missing, and the system looks fine the entire time.

If you only change one setting after reading this, make it that one, and then confirm it worked by checking the oldest-clip date a week later.

That drive is doing something a desktop drive is not built to do

A camera recorder writes continuously, from several cameras at once, all day and all night, forever. That is a genuinely unusual workload, and it is worth understanding why the drive inside the box is not the same kind of drive that is inside your computer.

Western Digital's own data sheet for its surveillance line is unusually blunt about it: "An average desktop drive is built to run for only short intervals, not the harsh 24/7 always-on environment of a high-definition surveillance system." The surveillance drives, it says, are "engineered specifically for surveillance to help withstand the elevated heat fluctuations and equipment vibrations within NVR environments," and carry "a workload rating of up to 180TB/year — up to three times that of desktop drives."

Workload rating is not marketing garnish. WD defines it as the amount of user data transferred to or from the drive in a year, and a camera system is a machine designed to transfer data continuously. Running a spare desktop drive you had lying around in a recorder is not an instant failure — it is a drive being asked, every single day, to do the thing its manufacturer says it was not built for.

So when a recorder's drive dies after two years, that is often not bad luck and not a defective product. It is the predictable end of a mismatch. If you are buying or replacing, buy a surveillance-rated drive; the price difference is small and the failure it prevents is the one that costs you the footage.

And in Southern California, the box is usually in the garage

Notice that heat appeared in the manufacturer's own description of what a surveillance drive is built to survive. Now think about where camera recorders actually get installed around here. The garage, a utility closet, the attic, a cabinet with no airflow — wherever the cable run was easiest and the noise would not bother anyone.

Those are the hottest, dustiest, least ventilated spots in the building, and inland — Riverside, Corona, Temecula, the whole desert side of our map — a closed garage in August is a meaningfully worse place to spin a hard drive than the room the computer is in. It is the same reason we tell people not to keep their only backup drive on the garage shelf.

This is not a reason to panic and relocate the box. It is a reason to give it airflow, keep it off the floor, keep it out of direct afternoon sun on a west-facing garage wall, and to treat the drive inside it as a consumable with a service life rather than a permanent fixture. Our garage-corner article covers the water and surge side of the same spot, and the earthquake piece covers the shelf it is sitting on; both are linked below.

The failure is silent, and that is the actual problem

Every hazard above shares one property, and it is the property that makes camera storage worth an article of its own: none of them announce themselves.

Your computer tells you when its drive is in trouble — Windows throws a warning, things get slow, you notice. A recorder in a closet has no screen, no one logged into it, and no reason to interrupt you. Reolink's troubleshooting list includes a drive that "intermittently halts recording from all cameras simultaneously," which is exactly the kind of fault that produces a system that looks perfect from the app and has holes in its history.

And the app is genuinely reassuring, which makes it worse. Live view: fine. Notifications: arriving. Cameras: all online, all green. Every signal a normal person would check is telling the truth about the present and nothing at all about the past. The recording layer is the only part of the system with no user-facing symptom when it fails, and it is the only part whose entire purpose is to be there later.

The ten-minute test, and it is not live view

Here is the whole article reduced to something you can do this evening. Do not check the live picture; the live picture is the thing that has been lying to you. Instead:

One — open playback and find a specific clip from several days ago. Not "is there a timeline," but a real moment: a car arriving, someone at the door, a light coming on. If you cannot find one, stop, because you have already found your problem.

Two — scroll back to the oldest footage that still exists and write that date down. That, not the number you were quoted, is your retention.

Three — export that clip and get it off the system. Save it to your phone or download it to a computer. This is the step people skip and it is the one that proves the whole chain works, because a system that can play footage back internally but cannot get a copy out is no use at all on the day you need to hand something to a police officer, an insurer or a neighbour.

Four — check whether any subscription involved is actually current, and check that overwrite is on.

If all four pass, your system does what you think it does. If any of them fails, you have found it on a calm evening instead of on the worst day of the year, which is the entire point.

What a sensible setup actually looks like

The answer is almost never local-only or cloud-only. Each covers the other's structural weakness precisely, which is unusual and worth exploiting.

Keep local recording as the spine. It is the copy that survives an internet outage, it holds far more history than any affordable cloud plan, it costs nothing per month, and it is the one you will use for ninety-nine per cent of real requests.

Add an off-box copy for the events that take the building. Depending on your hardware that might be a cloud clip service, uploads to a server or NAS elsewhere in the house, or a camera keeping its own card in parallel with the recorder. It does not need to hold everything — it needs to hold the important minutes somewhere the fire is not.

Put the recorder, the router and the modem or ONT on battery backup, so a power cut does not end both the recording and the uploading at once.

Use a surveillance-rated drive, give it air, and replace it on a schedule instead of on discovery.

And put a reminder in your calendar to redo the four-step test twice a year. A camera system is not an appliance you install once; it is a small piece of infrastructure with a moving part in it, and the only way to know it is still working is to ask it for something old.

The small-business version, which has one extra problem

Everything above applies to a shop, an office or a warehouse, with one addition: at a business, the recorder is usually in the back room, and the back room is usually where an internal problem happens. A system whose only copy is on a box that staff can reach is a system that can be edited.

The other business-specific gap is that nobody owns it. At a house, someone notices eventually. At a business the cameras were installed by a contractor who has moved on, the person who knew the password left, and the system runs unattended for years until the day it is needed for an incident, a claim or a dispute. That is also, routinely, the day everyone discovers there are eleven days of history rather than ninety.

If you run a business with cameras, the useful move is to write down four things and put them where the next person will find them: where the recorder physically is, how to log into it, how far back it actually goes, and how to export a clip. That document is worth more than another camera.

What we will not tell you, and why

We are not going to rank camera brands here. The right system depends on how many cameras, whether you can run cable, and whether you want a subscription, and a list would age badly and help nobody.

We are not going to quote subscription prices or plan names. They change, they vary by region, and a stale price in an article is worse than no price — check the vendor's current page.

We are not going to tell you how much footage a given drive holds for a given number of cameras. It depends on resolution, frame rate, compression and how much your cameras actually see, and any single figure would be wrong for most readers. The oldest-clip date on your own box answers the question honestly and specifically, which is why we keep pointing at it.

How we can help

We install and service cameras, outdoor access points, gate and driveway hardware and the cable runs and networking underneath them across our whole service area. When we set up a system we set up the recording too — a surveillance-rated drive, overwrite on, an off-box copy for the events that take the building, and battery backup on the parts that have to survive a power cut.

If you already have cameras and you do not know what is behind them, that is an extremely common place to be and a short visit to find out. We can tell you where your footage is going, how far back it really goes, whether the drive is healthy, and what it would take to make the recording as reliable as the live picture already looks. Get in touch and we will start with the four-step test — often we can walk you through it over the phone.