Gaming Studio Consolidating Box and Perforce

7 min

Perforce is the right tool for what it does — version-controlling engine assets, code, and binary game files across a large development team. But the marketing, cinematics, and community teams sitting alongside engineering usually aren't in Perforce day to day; they're producing trailers, capture footage, screenshots, and social clips, and that media typically ends up in Box instead, because it's what the rest of the studio uses for general file sharing.

The result is two systems with almost no overlap: source-of-truth game assets live in Perforce, understood mainly by engineers, while marketing's growing library of capture footage, trailers, and promotional video lives in Box, searchable only by whoever remembers the folder structure.

The Workflow Gap

  • Marketing media isn't code, but it's treated like generic files. Box handles documents and general files fine; it has no content-level search for video.

  • Perforce isn't built for marketing's use case. Cinematics and capture footage doesn't belong in an engineering version-control system, so it never ends up there — it lands in Box by default instead.

  • No searchable link between the two. Finding "every capture clip featuring the new character" means a manual hunt through Box folders, disconnected from the build or milestone it came from.

Consolidating the Media Side of the Pipeline

Studios making this move keep Perforce exactly where it is for code and engine assets, and move the marketing, cinematics, and capture footage side into Shade, where AI search indexes footage by scene content and visual detail — surfacing every clip featuring a specific character or environment without relying on manual tagging. Review and approval tools let creative directors and community managers sign off on trailer cuts and social clips in one place, and delivery links replace Box's link-sharing for getting approved content to publishers, platforms, and press.

What Changes for the Studio

  • Marketing media becomes searchable by what's actually in the footage, not folder naming conventions.

  • Engineering keeps Perforce — this isn't a replacement for version control, just the media side that never belonged there.

  • Faster trailer and social turnaround around major beats (reveals, updates, launches) when capture footage is instantly findable.

See Shade's comparisons for how it stacks up against general file storage like Box for media-heavy teams.