How to edit 8K 360° video on a phone with 6 or 8 GB of RAM

Why RAM is only part of the problem

A phone with 6 or 8 GB of RAM may be comfortable to edit on and still be unable to decode a particular 8K file. Resolution, codec, hardware decoder support and heat all matter. In our GoPro tests, the Galaxy A34 did not offer a decoder for the original HEVC panorama. Lite mode reduces analysis work; it cannot add a missing hardware decoder. Preparing the working copy on Windows avoids asking the phone to open that original.

A proxy is smaller, but it still contains the whole panorama

SphereCut PC creates an AVC working copy up to 2048 pixels wide from a stitched, monoscopic 2:1 SDR panorama. The duration and panoramic geometry stay aligned with the source. You can choose a new view, follow a subject or turn around later because the copy contains the whole sphere. A portrait crop made before transfer would throw away those other directions. Keep the full-resolution source on the PC until the final render is complete.

The three-step workflow

Install SphereCut on Android and extract the complete Windows companion package. The PC needs a compatible graphics driver for OpenGL 3.3 and enough disk space for the working copy and output. Start with a short clip to confirm your source format and export settings before committing a long recording.

1. On the PC, drop the stitched panorama onto the main tile and let the working copy finish.
2. Connect both devices to the same local network. In SphereCut on Android, choose Receive from PC (QR), scan the code and open the project. Select Lite for a lighter editing workload.
3. Make your framing, cuts and speed changes. In Export video, send the edit back to the PC. On Windows, choose Render from original.

What happened in our Galaxy A34 test

Our 14.181-second GoPro sample was a 7680 × 3840 HEVC panorama, 258,275,856 bytes on the PC. The phone received a 2048 × 1024 AVC copy of 15,312,248 bytes. The first returned edit was only 2,176 bytes. That particular video transfer was about 94% smaller than the source. These are measurements from one sample, not a guaranteed compression ratio. A long, noisy or fast-moving recording can produce a much larger working copy.

8K source detail is not 8K detail in every crop

The PC applies your camera directions to the original, rather than enlarging the phone's working copy. In the same test it produced a 7680 × 4320 landscape file, and the complete output decoded successfully. But a 360° source spreads pixels around the sphere. A narrow view uses only part of them. An 8K output size does not mean a close-up contains 8K of independent captured detail. Moderate framing often looks better than pushing the zoom as far as possible.

Keep the editing session light

Use Lite and the PC-prepared working copy. Leave enough storage for the project, avoid running other demanding apps alongside a long session, and let a hot phone cool down. Review a short export before rendering the entire film. If you export directly on the phone from the working copy, expect working-copy detail. For the original's detail, return the project to the PC. A faster PC can help rendering, but render time still depends on the source, output and hardware.