An hour of 8K 360° video can take roughly 45 to 135 GB, depending on the camera’s bitrate. That’s a wide range, but you don’t need to be a video engineer to plan for it: once you know the recording setting and how long you’ll film, a quick calculation will give you a useful estimate.
If you’re packing for a trip or filming an event, the question is simple: will your card and backup drive have enough room? Let’s work it out together.

MicroSD card photo by Koweja, dedicated to the public domain; via Wikimedia Commons.
What is bitrate?
Bitrate is the amount of data a video records or uses each second. Cameras usually show it in megabits per second, written Mbps. Think of it like the flow of water through a tap: a higher flow fills the bucket faster. At 200 Mbps, a video writes roughly twice as much data each second as one recorded at 100 Mbps, so a recording of the same length needs about twice as much space.
A higher bitrate gives the encoder more data to describe the scene and can preserve more detail, especially in complex motion. It doesn’t automatically make every video look better: the camera, resolution, codec, lighting and recording settings matter too. Some cameras use a variable bitrate, which changes with the scene, so the figure in a specification may be a maximum rather than the average for your clip.
One small distinction helps with the math: Mbps uses a lowercase b for bits, while MB/s uses an uppercase B for bytes. Eight bits make one byte, so 200 Mbps is approximately 25 MB/s. Your card capacity is usually shown in gigabytes (GB), a larger unit of bytes.
How to calculate 360 video storage per hour
To estimate a recording, divide megabits per second by eight to get megabytes per second, then multiply by 3,600 seconds in an hour. In decimal storage units, there’s a handy shortcut:
GB per hour ≈ bitrate in Mbps × 0.45
| Average bitrate | Approximate video data per hour | Approximate data for 30 minutes |
|---|---|---|
| 100 Mbps | 45 GB | 22.5 GB |
| 150 Mbps | 67.5 GB | 33.75 GB |
| 200 Mbps | 90 GB | 45 GB |
| 300 Mbps | 135 GB | 67.5 GB |
These are planning estimates, not promises about a specific clip. They use decimal gigabytes, where 1 GB is 1,000,000,000 bytes. Camera displays, operating systems and card makers may label capacity differently. Actual files can be smaller with variable bitrate encoding, or differ because of audio, container overhead, the selected mode, frame rate and scene complexity. Leave free space rather than planning to fill a card to its last gigabyte.
That adds up quickly. At 200 Mbps, an hour of source video is about 90 GB; four hours can approach 360 GB before exports, preview files or backups. The 8K label tells you the image resolution, but bitrate and duration are what you need for this storage estimate.
What camera bitrates mean in practice
Published maxima are useful ceilings, not a guaranteed average for every recording. DJI lists Osmo 360's maximum video bitrate as 170 Mbps and its panoramic video formats include 8K. Insta360's X5 specification table lists a maximum of 180 Mbps for regular video modes, with separate higher limits for certain timelapse and TimeShift modes. GoPro's MAX2 firmware announcement describes recording up to 200 Mbps, while GoPro's Labs announcement describes up to 300 Mbps. Check the exact mode, firmware and bitrate setting before applying those numbers to a shoot.
For a rough comparison, 170 Mbps corresponds to about 76.5 GB per hour at the maximum rate; 180 Mbps is 81 GB; 200 Mbps is 90 GB; and 300 Mbps is 135 GB. The 300 Mbps example is especially useful for high-bitrate planning, but it should not be treated as the default output of every camera or recording mode.

Photo by Laurabatanero, CC BY-SA 4.0, via Wikimedia Commons.
V30, V60 and U3: choosing a card for 360 recording
The SD Association defines Video Speed Class by minimum sequential write speed: V30 means at least 30 MB/s, while V60 means at least 60 MB/s under the class specification. Converted to bits, those are 240 Mbps and 480 Mbps. U3 also indicates a 30 MB/s minimum under its class, though speed-class requirements depend on both the host and card.
Those numbers are useful, but they don’t guarantee that every V30 card will work with every 240 Mbps recording mode. Camera firmware, card condition, file system, sustained performance, and the maker's compatibility testing all matter. For example, Insta360's X5 file-storage guidance calls for exFAT, UHS-I and V30 or above, and lists tested card models. DJI's Osmo 360 specification page also lists recommended microSD models. Use the exact camera's current list, format the card in the camera when its instructions say to, and do a sustained test recording before an important event.
V60 can provide more write-speed headroom, but it does not increase the camera's encoded bitrate or guarantee longer recording. Capacity determines the run time; sustained write performance determines whether the card can keep up reliably. A large but incompatible card is a poor bargain if it drops frames or stops a take.
Estimate recording time from card capacity
Divide the card's usable decimal capacity by the estimated GB per hour. A nominal 256 GB card at 200 Mbps gives a theoretical 2.8 hours; at 300 Mbps, about 1.9 hours. Real usable time is lower because of formatting, other clips and the need to leave room for the camera's file system. Even with that breathing room, the estimate helps you decide whether to pack a second card.
If the camera splits long recordings into segments, that changes how clips appear in the file browser, not the total data created. Keep every segment and companion file together until you have verified the copy. For long shoots, label cards, rotate them in a known order and avoid deleting anything in-camera until two verified copies exist.

Photo by Sam Frazier, CC BY-SA 4.0, via Wikimedia Commons.
Build a raw archive and a web-ready copy
Treat the original camera files as the source archive. Copy them to a working drive, verify the copied files open in the maker's software, then keep a second copy on another physical device or a separate backup service. A stitched or reframed export is useful for delivery, but it cannot replace the original if you later need different stitching, reframing or color settings.
For a client or web viewer, create a separate delivery export at the resolution and bitrate the project needs. This smaller, stitched copy is easier to upload and stream, while the original remains available for future revisions. Don't delete originals just because a preview played correctly.
A cloud host is useful for the web-ready file, not necessarily for every untouched camera master. Review the account's file limits, storage allowance and privacy controls before uploading a whole day of source footage. Mirame360 lets you explore hosted 360° media and create an account for sharing browser-ready work. Keep a local archive even when the online version is live.
A quick storage plan before leaving
- Multiply the camera's stated maximum bitrate by 0.45 to estimate GB per hour; use a lower realistic average only after checking your own recordings.
- Multiply the result by the planned recording hours, then leave free card capacity for overhead and extra clips.
- Use a manufacturer-approved card with at least the required speed class, and test a long take in the intended mode.
- Copy originals to two separate locations before reusing cards.
- Upload the stitched deliverable separately from the raw archive, and test it in the browser before sending the link.
A little planning before you leave gives you more time to enjoy the shoot and less time worrying about a full card. Estimate the hours you expect to record, bring a compatible spare card if you need one, and make your backup copies before clearing the originals. The numbers don’t need to be perfect; they just need to give you enough room for the day ahead.
