Your Security Cameras May Show Live Video but Record Nothing: Run This 20-Minute Test

A live camera picture is not proof that your system is saving usable evidence. A home or small-business camera can stream perfectly while recording is disabled, a schedule is wrong, a cloud plan has expired, local storage has failed, or the clock is hours off. You usually discover that problem only after a theft, delivery dispute, vandalism incident, or workplace issue—when the missing footage is already expensive.

This guide gives Treasure Coast homes and small businesses a vendor-neutral, 20-minute test for proving that a camera can record, retain, find, play, and export a useful clip. Run it on the exact system you own; cloud cameras, battery cameras, doorbells, microSD cameras, NVRs, and NAS recorders behave differently.

The costly problem: “I can see live video” creates false confidence

Live View and recording are separate functions. Official support documentation shows just how many ways the two can diverge:

• Ring: recorded-video review depends on a compatible subscription, and events that happened before the subscription began are not retroactively recorded. Ring also says an offline device cannot record events. See Ring’s guides to managing videos and fixing offline devices.
• Google Nest: event history and 24/7 history are different. Event-only service stores qualifying events rather than every quiet minute. Export options also vary by app and camera generation. See Google’s explanations of event and continuous video history and saving clips.
• Local recorders: a camera may be online while its NVR disk, NAS folder, SD card, USB storage, channel assignment, or recording schedule is not working. Reolink’s official outage guidance, for example, shows that behavior depends on the exact camera, power source, network state, hub, and storage method—not on a universal “local versus cloud” rule. See Reolink’s power and internet outage guidance.

A notification is not proof either. An alert, a thumbnail, a playable clip, a retained clip, and an exportable evidence file are five different results. The test below checks all five.

Who should run this test?

You are especially affected if:

• You use a battery doorbell or Wi-Fi camera that records only on motion.
• Your cloud trial or camera subscription recently changed.
• You replaced a router, changed Wi-Fi credentials, moved a camera, installed an app update, or had an installer visit.
• Your NVR, NAS, SD card, or USB storage is more than a few years old or has shown disk warnings.
• You need footage for a storefront, cash area, entrance, parking area, stockroom, delivery point, or home exterior.
• Your cameras, router, access point, NVR, and modem do not share the same backup-power plan.
• You have never exported a clip and played it on another device.

You may not have a fault if:

• An intentionally live-only monitor has no recording requirement.
• An event-only timeline has quiet gaps and a known test event records correctly.
• Old footage disappeared after the documented retention period.
• A camera is intentionally in privacy, home, disarmed, or “never record” mode.
• Remote viewing is down while a tested local recorder continues recording.

Those conditions can be normal, but they are still the wrong configuration if you expect the system to preserve evidence.

Before you start

Gather a phone with automatic date and time enabled, administrator access to the camera or recorder, and a second device on which to test the exported file. Make a simple worksheet with one row per camera:

• Camera name and physical location
• Model and storage destination: cloud, microSD, hub, NVR, or NAS
• Expected mode: always, motion/event, schedule, or manual
• Expected retention period
• Power source and what happens if power or internet fails
• Test-event time, playback result, export result, and clock difference

The 20-minute security-camera evidence test

Minutes 0–3: Prove recording is enabled

1. Open Recording, History, Events, Playback, or Storage settings—not only Live View.
2. Write down the current mode for every camera: continuous, motion/event only, scheduled, manually armed, privacy/home, or disabled.
3. Confirm today and the current time fall inside the intended schedule.
4. For event recording, verify the needed triggers are enabled: motion, person, vehicle, package, doorbell press, or another supported event.
5. For cloud cameras, confirm the recording plan is active and includes the camera you are testing.
6. For local systems, check disk/card status, free space, recording destination, overwrite/rotation rules, and channel errors.
7. Take screenshots of the working settings so you have a baseline.

Fail the test if you find “never record,” an inactive schedule, an expired plan, disabled detection, a missing/full disk with overwrite disabled, storage errors, or a camera mapped to the wrong recorder channel.

Minutes 3–6: Create one known event

1. Stand where a real face, person, vehicle, package, doorway, or transaction would need to be visible.
2. Note the exact time shown on your phone.
3. Walk through the center of the detection area, then its outer edge.
4. Pause for a few seconds where identifying detail matters. For a doorbell, press the button as well as creating motion.
5. Repeat from the opposite direction when practical.
6. Wait the normal processing or cloud-upload interval for your model.

Example: A storefront camera may alert when a person reaches the door but begin recording after the face has passed. A driveway camera may capture a car yet lose the license plate to glare. A doorbell may record the button press but not ordinary motion because those are separate triggers. Test the scene you actually need, not just a hand waved inches from the lens.

Minutes 6–9: Find and play the recording

1. Leave Live View and open the system’s actual history or playback screen.
2. Find the event by its known time rather than relying only on the notification.
3. Play the clip from beginning to end.
4. Confirm the correct camera recorded, the clip starts before the critical action, it lasts long enough, and both test passes appear.
5. Look for blind spots, delayed starts, short clips, blur, compression blocks, infrared glare, reflections, backlighting, rain, foliage, insects, or a subject too small to identify.

Fail the test for a missing event, a thumbnail with no playable video, wrong camera/channel, corrupt playback, a clip that begins too late, or an image that exists but is not useful.

Minutes 9–11: Check the clock and time zone

Compare the clip with your phone’s synchronized clock. Verify the date, Eastern Time offset, daylight-saving setting, on-video overlay, application timeline, recorder clock, and exported filename. If the system offers NTP or automatic time synchronization, confirm it is enabled and healthy.

A wrong clock can make it difficult to correlate video with an alarm, access-control record, receipt, vehicle event, or police timeline. Measure and record any difference. Do not silently change the time on footage that may matter to an existing incident.

Minutes 11–14: Export the clip and play it elsewhere

1. Export the test clip through the same workflow you would use after a real incident.
2. Save it outside the camera app or NVR, such as an approved computer folder or external drive.
3. Open the exported file on a second device with an ordinary media player.
4. Verify video, audio if intentionally and lawfully enabled, orientation, duration, and timestamp.
5. Record the filename, camera, time range, export time, and who performed the export.

Good: The file opens independently, contains the complete event, has the expected resolution, and can be copied without proprietary software.

Bad: The export is zero bytes, corrupt, missing the important seconds, locked inside an app, or usable only after installing an unknown codec or granting unnecessary cloud access.

Minutes 14–17: Measure real retention

1. Find the oldest recording that actually plays.
2. Compare its age with what you expected from the plan or storage estimate.
3. Check whether retention is per camera, per event, or shared across all channels.
4. Confirm whether the system overwrites the oldest clips automatically or stops when full.
5. For an NVR/NAS, review disk-health and recording-status warnings; do not assume a healthy RAID array is a separate backup.

Higher resolution, higher frame rate, more cameras, continuous recording, and extra audio all consume storage faster. A plan labeled “30 days” may also treat continuous and event history differently. Trust the oldest playable file, not only the marketing label.

Minutes 17–20: Test outage behavior safely

First document the expected design. Which devices need power: camera, PoE switch, Wi-Fi access point, router, modem/ONT, hub, NVR, NAS, and external drive? Which need internet? A battery camera may stay powered while its Wi-Fi router or hub goes dark.

1. If an approved maintenance window is available, briefly disconnect only the internet/WAN path—not power to the entire building.
2. Create a second known event.
3. Restore connectivity and check whether the event exists locally, uploads later, or is missing.
4. Do not assume the result applies to every camera model in a mixed system.

Cloud-only systems may stop recording without internet. Some local SD, hub, or NVR systems continue if the camera and storage retain power. Some supported models cache limited footage and upload after reconnection. The only safe conclusion comes from the documentation and a controlled test of your exact installation.

If outages are common, review our guides to testing a UPS battery backup and building a backup internet plan.

Secure the camera system after the recording test

The Federal Trade Commission’s camera-security guidance recommends checking encryption, changing default credentials, updating camera and router software, securing Wi-Fi, and considering a separate network for cameras rather than placing them beside computers and printers. The FTC also recommends limiting shared access instead of giving everyone the administrator login.

• Use a unique password for the camera account; never reuse your email or banking password.
• Enable multi-factor authentication. The FTC explains why in its two-factor authentication guide.
• Remove former employees, installers, tenants, or family members who no longer need access.
• Prefer named viewer accounts and least privilege over a shared administrator credential.
• Install firmware and app updates—but only after exporting incident footage, checking release notes, and planning how to verify recording again.
• Secure the router and Wi-Fi. Our router security checklist covers firmware, encryption, default settings, remote management, and replacement planning.

NIST’s consumer IoT cybersecurity baseline also emphasizes data protection, access control, secure software updates, device-state awareness, and clear support information. Those controls do not prove a camera is recording, but they help protect the footage and make failures easier to identify.

Florida privacy and audio caution

Do not aim cameras into bedrooms, bathrooms, changing areas, or other places where people reasonably expect privacy. Avoid capturing more of a neighbor’s property than the security purpose requires, and use privacy masks where available.

Audio is especially sensitive. Florida’s interception law includes an all-parties-prior-consent provision in specified circumstances, while Florida’s digital-voyeurism law addresses secret imaging in privacy-sensitive settings. Read the actual Florida Statutes section 934.03 and section 810.145. A sign, outdoor location, or device setting does not automatically answer every legal question.

A practical maintenance schedule

This schedule is a practical recommendation, not a government-mandated interval. Increase the frequency where video protects high-value inventory, cash handling, entrances, vulnerable people, or legally sensitive operations.

Frequently asked questions

Why can I see Live View but find no recordings?

Recording may be disabled, outside its schedule, set to event-only, in privacy/home mode, dependent on an expired plan, or unable to write to local storage. Check recording settings and create a known event.

Does a motion notification prove the video was saved?

No. Find the event in history, play the full clip, and export it. A notification or thumbnail is not the same as a retained video file.

Will my cameras record when the internet is down?

It depends on the exact model, power source, and storage design. Cloud-only cameras may stop. Some SD, hub, or NVR systems continue locally if all required equipment remains powered. Test your installation safely.

Will a battery camera work during a power outage?

The camera may remain powered, but its Wi-Fi access point, router, hub, modem, or local recorder may not. Map the entire path.

How do I know whether an NVR hard drive is really recording?

Check disk and channel health, create a known event, find it in playback, export it, and play the file on another device. A spinning disk or green status light is not enough.

How long is footage actually retained?

Find the oldest clip that still plays. Compare that real age with your expectation, then review per-camera retention, event-versus-continuous history, resolution, frame rate, and overwrite rules.

Should I turn on camera audio?

Not automatically. Audio can create significant privacy and legal issues. Disable it unless there is a documented need and you have confirmed the applicable notice, consent, and legal requirements.

Is a professionally installed system automatically reliable?

No. Disks fail, schedules change, plans expire, clocks drift, passwords remain with old installers, and network changes break recording paths. Professional installation still needs periodic verification.

Your next action

Pick the most important camera today and create one known event. Do not stop until you can find it, play it, export it, open it elsewhere, and confirm the time. If any part fails, treat the system as not evidence-ready until the failure is corrected and the complete test passes.

For help auditing cameras, Wi-Fi, NVR storage, account security, or outage protection in Port Saint Lucie, Jensen Beach, Fort Pierce, or Vero Beach, review our small-business IT services, contact The IT Guys, or schedule an appointment.