Use cloud snapshot storage when the product mainly needs a still image to verify that an event occurred. Use cloud video storage when an operator must understand what happened before, during, and after the event. Imou’s cloud-record query accepts cloudType values snapshot and video; the right choice depends on evidence needs, device and service availability, and retention policy—not an invented universal price comparison.
Why this matters
A snapshot and a video clip answer different questions. A still can confirm that a person, vehicle, or scene was present at a moment. A recording can reveal approach, sequence, duration, and outcome. Selecting storage only by file size can leave an incident workflow without enough context; selecting video for every workflow can retain more data than the product actually needs.
There is no public price table established by the cited API page, so this FAQ does not quote per-camera rates or promise a free package. Commercial terms and service availability must be checked for the relevant account, region, device, and package.
Decision table
| Product question | Snapshot storage | Video storage |
|---|---|---|
| “Did an event appear to occur?” | Often the direct evidence format | Can answer, but may be more context than needed |
| “What led up to and followed the event?” | A single image is usually insufficient | Better aligned with sequence and duration |
| Human review speed | One frame is quick to scan | Reviewer must inspect a time segment |
| Evidence richness | Moment and visible scene | Motion, order, duration, and surrounding context |
| Data handling | Still-image retention policy | Video retention and access policy |
| API query selector | cloudType: "snapshot" |
cloudType: "video" or omit it because the documented default is video |
This table is an architecture decision aid. It does not claim that every camera, account, or package offers both storage modes.
Reference architecture
Device event
|
+--> snapshot path --> verification queue --> reviewer decision
|
+--> video path -----> incident timeline --> investigation/export workflow
Your backend:
tenant authorization -> device/channel scope -> cloud record query
Imou OpenAPI:
getCloudRecords(..., cloudType="snapshot" | "video")
Your application should keep storage selection separate from access authorization. A sub-account querying records needs the minimum permission documented by the interface: RecordReplay on the relevant cam:serial-number:channel-number. Device capability and an active service still determine whether records exist.
Six steps to choose and implement
- Write the evidence question. If the acceptance criterion is “show one visual confirmation,” evaluate snapshot storage. If it is “reconstruct the incident,” evaluate video.
- Define the review workflow. Decide who can view the material, how quickly it must be found, and what action follows. Do this before selecting retention.
- Check actual availability. Confirm the target device/channel and the account’s cloud-storage service. Do not infer availability from another device or region.
- Keep queries server-authorized. Your backend should verify tenant and channel access before it calls the cloud-record API. Administrator credentials and AppSecret must not enter client code.
-
Query the intended media type. Call
getCloudRecordswithdeviceId,channelId,beginTime,endTime,count, and the optionalcloudType. Use the documented valuessnapshotorvideo; video is the default. - Validate with real incidents. Test whether the selected media answers the original evidence question, then review privacy, retention, and access controls before rollout.
API example
The following shows only the relevant params portion of the signed request:
{
"params": {
"token": "AUTHORIZED_ACCESS_TOKEN",
"deviceId": "DEVICE123",
"channelId": "0",
"beginTime": "2026-08-31 09:00:00",
"endTime": "2026-08-31 10:00:00",
"count": 30,
"cloudType": "snapshot"
}
}
For video, set cloudType to video or rely on the documented video default. getCloudRecords displays matching cloud records in reverse order and permits at most 30 per query. Those retrieval rules are the same reason a production UI should paginate rather than assume one response represents a complete incident window.
A mixed model can be valid
The choice does not have to be one global switch for the entire product. For example:
- a high-volume triage view can begin with snapshots;
- a reviewed event can link to available video context; and
- selected sites with investigation requirements can use a video-oriented workflow.
That is product architecture guidance, not a statement that one storage package automatically upgrades another or that every event has both media types. Confirm actual records through the API and subscribed service.
Limits and pitfalls
Treating a still as a timeline
A snapshot cannot show events outside its captured moment. Do not describe it as complete incident context.
Treating all video as complete evidence
A returned clip covers its documented begin and end times. Gaps, service state, device availability, and the selected query window still matter.
Publishing unsupported pricing
Do not state public unit prices, savings percentages, or universal free entitlements unless an approved live commercial source supplies them. The technical docs cited here define API behavior, not a global price list.
Assuming universal support
Storage depends on the device, channel, account, region, and subscribed service. Query and test the target deployment.
Mixing media type and record type
cloudType chooses video or snapshot for the query. The returned video-record type field describes documented recording categories. They are different concepts.
Ignoring authorization and privacy
Snapshots and video can both contain sensitive scenes. Apply tenant checks, narrow channel permissions, audit access, and establish retention/deletion procedures appropriate to your deployment.
Recommendation
Start from the decision the user must make:
- Event verification: prefer a snapshot-oriented design when one frame is sufficient.
- Full incident context: prefer video when sequence, duration, and surrounding activity matter.
- Mixed workflow: use each format for its specific review stage, after confirming service support.
Register at Imou Open Platform to test cloud-record queries with your target devices and services before finalizing the retention model.
Top comments (0)