How do animation studios share files without the cloud?

They keep files on individual workstations and move them directly over the local network instead of syncing through a cloud service. A LAN transfer tool lets any machine send a shot, scene or asset to another at wire speed, with everything staying inside the studio. Larger facilities add shared storage (a NAS or SAN) for the render farm; small studios often just use direct artist-to-artist transfer.

Why is cloud storage bad for animation and VFX files?

Two reasons: frame sequences are thousands of small files, and cloud sync pays a per-file overhead plus an upload round-trip on each one, so a 20 GB shot in 8,000 frames syncs far slower than a single 20 GB file. And unreleased client work under NDA should not be stored on a third-party server. Direct LAN transfer avoids both problems.

Can Oxolan handle an animation studio's file sizes?

Yes for the artist-to-artist layer: it moves multi-gigabyte scenes, caches and frame folders between workstations at 60–115 MB/s on gigabit, resumes 60 GB+ transfers after a drop, and locks scene files so two artists cannot overwrite the same one. It does not replace render-farm shared storage or work between two buildings — it is the fast, private, in-studio transfer layer.

How Animation Studios Share Files Between Artists Without the Cloud

The File Problem in an Animation Studio

An animation or VFX studio does not share "a file" — it shares a constant stream of them. In a single day, artists pass around scene files, texture and asset libraries, reference footage, playblasts for review, and rendered frame sequences where one shot can be tens of gigabytes across thousands of individual images.

Three things about that workload break the tools most offices reach for:

Frame sequences are many small files. A rendered shot is one image per frame — a few seconds of animation is hundreds of files, a full shot is thousands. Cloud sync clients choke on this: each file carries per-file overhead, so a folder that is 20 GB but 8,000 frames syncs far slower than a single 20 GB file.
The files are large and numerous. Texture libraries, cache files (Alembic, VDB), and EXR output are both big and plentiful. Upload-limited cloud round-trips turn a two-minute LAN copy into an afternoon.
The work is confidential. Unreleased client IP under NDA should not be sitting on a consumer cloud account.

What Small Studios Actually Do

Large facilities run shared storage (a SAN or a fast NAS) with the render farm and every workstation mounted to it. That is the right answer at scale — but it is expensive and needs someone to run it. Smaller studios and teams work differently: files live on individual workstations and move between them directly over the local network.

That direct, artist-to-artist layer is where a LAN transfer tool fits. Instead of routing a shot through the cloud or walking a drive between rooms, you send it straight across the switch:

Every workstation stays visible. Machines running Oxolan discover each other in about 300 ms and stay in a sidebar — animator, lighter, comp, supervisor — even when Windows' own network discovery breaks after an update.
Shots move at wire speed. A 30 GB EXR sequence crosses a gigabit network in roughly five minutes at 60–115 MB/s. If a transfer drops, it resumes from where it stopped instead of restarting at frame zero.
Files stay in the building. Transfers are encrypted machine-to-machine (TLS 1.3) and never touch a third-party server, which is the answer an NDA is looking for.

Frame Sequences Specifically

The single biggest workflow trap is treating a frame sequence like a folder of loose files. Whatever you use, move the sequence as one job, not file by file:

With cloud sync, the per-file overhead is the killer — see why cloud sync is slow for office files. Zipping a sequence before an occasional cloud send helps, but it is a workaround.
With a LAN transfer, sending the whole folder streams the frames over one connection, so 8,000 frames behave more like one large transfer than 8,000 small ones. This is covered in depth in transferring EXR frame sequences between workstations.

A Realistic Small-Studio Setup

Wire the workstations. Anything moving frames or caches belongs on gigabit Ethernet, not Wi-Fi — the speed difference is decisive for large transfers.
Decide where the "current show" lives. A NAS for the working set if you have one; otherwise each artist owns their working files and hands off what others need.
Use direct transfer for handoffs. Sending selects, scene files and shots between machines without staging them on a server keeps the daily flow fast.
Keep an off-site backup. LAN-only is fast and private, but it is not a backup — mirror finished work somewhere separate.

Where Oxolan Fits (and Where It Does Not)

Oxolan replaces the artist-to-artist layer: getting shots, scenes, textures and reference between workstations without mapped drives, sync clients, or drive-walking, with file locking so two artists cannot overwrite the same scene. It is Windows and macOS, which covers mixed studios. It does not replace render-farm storage or work between two separate buildings — it is LAN-only by design. For a small studio in one space, that is exactly the layer that hurts most, and the one with the cleanest fix.