How to Edit 4K Video Remotely on a Slow Internet Connection

A remote editor can have enough processing power for a 4K project and still spend the afternoon waiting for footage to download. Opening a clip for the first time puts the most pressure on the connection: the application needs data that hasn't reached the computer yet, while a call or another person's upload may be using the same network. Download smaller editing proxies before the session when the originals would take too long to arrive. You can then assemble the edit from those local files and arrange delivery of the originals to the workstation that will finish it. If you stream media while editing, compare the files' data rates with the bandwidth left after other network traffic. The example below uses two hours of 4K footage and a 20 Mb/s connection to calculate transfer times, local storage needs, and a workable handoff schedule.

Measure the connection and check the footage bitrate

Start with the footage's bitrate: the amount of data required for each second of media. Resolution alone doesn't supply that number. Two 4K clips can have very different bitrates because their recording codecs, compression settings, frame rates, and audio differ. Use the file information in your editing application to inspect clips from each camera format you use. If the recording uses a variable bitrate, an average helps estimate total transfer size but can conceal more demanding passages. Include the busiest footage and the largest number of simultaneous streams in your playback check. Check upload and download separately using the workstation and network you intend to use. An advertised internet plan is a ceiling, while an actual file transfer shows what reaches that computer over time. Repeat the check during normal working hours. Note interruptions and large swings in speed, since a good average can hide repeated stalls. Use wired Ethernet where practical, and pause unrelated large transfers during the check. For editing from an Aspect drive, open the clips in your editing application and play the sequence you intend to work on. Include cuts, transitions, and multiple camera angles so the check reflects a normal editing session.

Build a bandwidth budget with consistent units

The distinction between bits and bytes matters. Mb/s means megabits per second; MB/s means megabytes per second. There are eight bits in a byte, so 20 Mb/s equals 2.5 MB/s before any additional losses. This example uses decimal storage units: one GB is 1,000 MB, or one billion bytes. Suppose the project has two hours of recorded source material. For this calculation, the originals average 200 Mb/s and the proxies average 8 Mb/s, including audio. Substitute the bitrates from your own files when planning a transfer. For this example, file size in GB equals bitrate in Mb/s multiplied by duration in seconds, divided by 8,000. Two hours is 7,200 seconds.

Media representation	Assumed bitrate	Size for two hours
4K camera originals	200 Mb/s	180 GB
Smaller editing proxies	8 Mb/s	7.2 GB

Suppose your connection sustains 20 Mb/s of usable download throughput. Reserving 5 Mb/s for other traffic and variation leaves 15 Mb/s for media. Increase that reserve if other people share the connection or your measured download speed varies substantially. A single 8 Mb/s proxy stream fits inside the allowance. Two simultaneous streams require 16 Mb/s, which exceeds it. A four-camera view reading four such streams requires 32 Mb/s, exceeding even the connection's full assumed throughput. Multicam therefore needs a different plan: lighter proxies, fewer active streams, or media downloaded before the session.

A single proxy stream can pass through the narrow connection while several simultaneous streams pile up.

The 200 Mb/s original is unsuitable for sustained uncached playback on this connection. Even if some footage has already buffered, a long enough first-time read will exhaust that head start. Increasing the cache limit doesn't change the arrival rate of new bytes. For a full download, the ideal transfer time in seconds equals file size in GB multiplied by 8,000, divided by usable throughput in Mb/s.

Complete download	At 20 Mb/s	At the 15 Mb/s media allowance
180 GB of originals	20 hours	26 hours 40 minutes
7.2 GB of proxies	48 minutes	64 minutes

These are minimum transfer times at constant throughput. They exclude interruptions, proxy generation, validation, and any remaining transfer overhead. Use the actual folder size once files exist, and leave extra time before a booked session.

Choose proxies for assembly and plan the originals for finishing

For this project, download the 7.2 GB proxy set before editing. The connection could stream one proxy at a time, but local files also let the editor jump between untouched clips and play several camera angles without exceeding the available bandwidth. A proxy is a smaller editing representation linked to the source clip. Select a format that the editor's computer can decode comfortably as well as one that fits the transfer budget. A highly compressed file can save network capacity while requiring more decoding work. If playback still stutters with the file fully local, investigate the workstation, effects, and drive instead of treating every pause as a network problem. The proxy preset also affects file size. For example, Final Cut Pro offers ProRes 422 Proxy or H.264 and a range of frame sizes. Generate a few clips with your chosen preset, then use their bitrate or complete size in place of the 8 Mb/s figure above. You can copy uploaded videos from Aspect as smaller MP4 proxies and attach them to the original clips in Premiere. If the edit needs a particular codec, frame rate, duration, or audio layout, generate proxies in Premiere with the corresponding preset. Check timecode and clip identity when attaching them, so the application switches between the same frames in the proxy and original. Keep the camera originals available for finishing. Decide early which workstation will perform that stage and when its original media will arrive. Switching an application back to originals does not remove the transfer requirement, and a lower playback-resolution setting doesn't create smaller source files.

Budget for both cached data and complete pinned files

Aspect's automatic cache retains recently accessed portions of media. When it needs room, it can remove older cached data and download it again later. The cache management guide explains how to set its capacity and location, and why increasing it can help when an editor repeatedly revisits the same footage. That working cache is different from a complete offline media set. Pinning downloads whole selected files and keeps them available locally until unpinned. Plan for those complete files as well as the automatic cache and your editing application's own generated media. Don't assume that choosing a 20 GB cache limit caps all local storage used by the workflow.

Local storage is shared by cache, pinned media, project assets, and generated files.

Suppose your laptop has 120 GB free after its operating system, applications, and existing files. A provisional allocation could be:

Local storage purpose	Planned allowance
Aspect automatic cache	20 GB
Complete pinned proxy set	7.2 GB
Pinned project files, separate audio, graphics, and references	5 GB
Editing application cache, temporary media, and exports	35 GB
Space left unallocated	52.8 GB

The supporting-file and application allowances are assumptions to replace with the project's real needs. A render-heavy sequence can exceed them. Check available storage again after pinning and after generating substantial renders, rather than treating the first estimate as permanent. The complete 180 GB original set won't fit in the laptop's starting 120 GB of free space. Either supply additional suitable storage, download only the original files needed for a defined finishing task, or finish on a workstation with sufficient capacity. Pinning a long source clip still requires its complete size, even if the timeline uses only a few seconds.

Finish pinning before relying on offline playback

Install the Aspect desktop app for macOS or Windows and mount the project. Import and open media through that drive so the editing application continues using the same paths when you work offline. Before the session, identify the actual files the sequence depends on: proxies, audio, graphics, references, project files, and any originals still in use. Follow the pinning guide, leave the desktop app running, and wait until the selected content is fully available locally. Check for transfer errors and confirm remaining disk space. Then reopen the sequence and inspect picture and audio with proxy playback enabled. After saving your work, briefly disconnect the network and repeat the relevant playback checks. Include a seek into the end of a long clip and the busiest multicam section. A folder opening successfully does not prove that every media dependency is present.

A project folder can be present while a required media item is still missing from the sequence.

Pinning a project file does not pin the footage it references. It also does not prepare an editing application's online project service for offline work. Establish the application's offline procedure and agree who owns the edit before disconnecting.

Schedule the upload before promising the handoff

The editor's download budget is only half the schedule. If the shoot location has 5 Mb/s of usable upload throughput, the same 180 GB of originals takes an ideal 80 hours to upload. The 7.2 GB proxy set takes 3 hours 12 minutes, excluding generation and checking. When originals are still at the shoot location, generating proxies there can bring the first usable edit forward. Upload the urgent proxy set, project information, and supporting audio first. Keep the originals backed up, and arrange their transfer over a better connection or through a physical delivery that meets the finishing deadline. Cloud-generated proxies become useful after the originals arrive and processing completes. They can't shorten the initial transfer of originals that remain on a camera card or local drive. Aspect's uploading guide describes per-file progress, pause and resume, and background processing after upload; include that processing stage in the handoff plan. If your editor needs to start before the full shoot arrives, agree on a first delivery that contains everything they need for one task. For example, complete an interview's proxies and separate audio before uploading the rest of the day's footage. The receiving editor should confirm that those files open and match the project before the sender treats that part of the handoff as ready. The return trip also needs time. A ten-minute review export at a total bitrate of 10 Mb/s is 750 MB. At 5 Mb/s upload throughput, that file takes at least 20 minutes to transfer. Rendering it just before the review call leaves no room for the upload, processing, or a playback check.

Rehearse the session and the return to shared work

Before the first editing session, try the operations that read the most media: opening a new bin, seeking into untouched clips, playing transitions, checking separate audio, and showing several camera angles. Watch for application background jobs that scan an entire library. Aspect's Premiere guide recommends limiting automatic waveform generation, media analysis, and transcription when those jobs would trigger unnecessary reads. Use these checks to make the final session decision:

If new media plays consistently with room in the bandwidth budget, use streaming with a suitable cache.
If repeat playback is good but new clips stall, prepare more media locally or use a smaller proxy representation.
If the connection is unreliable or the session can't tolerate stalls, finish pinning the required files before starting.
If fully local media still struggles, address decoding, effects, or storage performance before changing the transfer plan again.

After an offline session, reconnect and allow new media, exports, and project saves to finish synchronizing. Confirm their availability from the shared project before the next person starts work. Adobe or Blackmagic project collaboration still needs its own change-sharing process; shared media access does not automatically reconcile competing edits. For the example project, the workable plan is to prepare and pin the proxy set, reserve local room for the edit, and arrange a separate original-media transfer for finishing. The editor can assemble the cut from local proxies while the originals travel to the finishing workstation.

FAQ

There is no universal speed requirement because 4K describes image dimensions rather than a file's bitrate. Add the bitrates of the streams your editing application reads at the same time, then compare that demand with the connection's sustained usable download speed. Leave room for other traffic and test seeking as well as continuous playback. If the connection cannot sustain the required uncached reads, use smaller proxies or complete local downloads before editing.

A 20 Mb/s connection can support some proxy workflows. For example, reserving 5 Mb/s for other traffic leaves room for one 8 Mb/s proxy stream, while two such streams exceed that allowance. A 200 Mb/s original needs more bandwidth than this connection can supply for sustained playback. Pin the proxies before editing if you need multicamera playback or expect the connection to drop.

A larger cache can retain more previously accessed media and reduce repeated downloads. It cannot make uncached data arrive faster than the connection allows, and a cache may contain only portions of a file. Use completed pinning when the full file must remain available locally, and make sure the workstation and local drive can play the chosen codec.

Pin the project files and every required media dependency, including attached proxies, audio, graphics, references, and any originals the session will use. Wait until pinning finishes, check for transfer errors, and verify that the sequence opens and plays from the mounted drive while offline. Pinning a project file does not pin its referenced media or make an editing application's cloud collaboration service available offline.

Proxy editing can preserve the original-based finishing workflow when proxies are correctly associated with their camera originals. Confirm matching identity, frame rate, timecode, duration, and audio layout before the edit. At finishing, make the originals available, select the application's original-media mode and appropriate export settings, and inspect the resulting file. A low-resolution proxy alone cannot supply the detail of the camera original.

Calculate the upload time before promising an editing start time. Generate and check editing proxies where the originals are already stored, send the urgent proxy set first, and schedule the originals through a connection or physical delivery route that can meet the finishing deadline. Cloud-generated proxies do not shorten the initial transfer of originals that have not yet reached the cloud. Include processing, verification, and the receiving editor's download time in the schedule.