A trailer named final.mp4 may not be the one approved for a publisher meeting. It might show an old release window, predate a rating change or include footage cleared for one territory but not another. A useful file system puts those differences in view before anyone downloads or sends the video.
Game marketing assets pass between studios, publishers, agencies and event organizers. A screenshot might go from a capture artist to a social manager, then into a press kit and onto a conference screen. The point of organizing files is to help each person find the current version and know where it can be used—not to keep a drive looking tidy.
Organize around work people actually need to retrieve
Before moving files, write down the questions colleagues ask under deadline. Where is the approved logo? Which gameplay clips can a publisher use? What creative ran in a particular market? Where are the editable files for the event booth graphic? The answers show which categories need permanent homes.
A shared workspace for one game might start with Brand and product facts, Source assets, Working campaigns, Approved distribution, Partners and events, and Archive. Give each a defined purpose. Source assets hold original captures and design files; approved distribution holds exports others can publish. That separation makes it less likely a work-in-progress trailer will end up in a media kit.
Within campaigns, group files by initiative and deliverable rather than adding a top-level folder for every platform. Campaigns / Expansion Launch / Store Assets, for example, could hold storefront packages for several markets. Keep the brief, approvals and final creative together at campaign level, while making reusable files easy to find in the approved-assets area. If your storage system supports shortcuts, use those rather than maintaining independent copies.
Leave the full historical cleanup for later. Start with active work and frequently requested assets; old drives can remain searchable as a dated archive while the team settles its rules for new files.
Give every folder a purpose and an owner
A folder tree is no help if no one knows what belongs in it. Put a short note at the top of each major area: what goes in, what stays out and which role maintains it. The approved-assets area, for example, should contain only files that have passed the necessary brand, legal, rating and partner reviews. Its owner also needs to remove or supersede files when the details change.
Assign responsibility to roles rather than relying only on individual names. A product marketing lead might own the product-facts sheet, an art lead the master key art and a regional marketing lead the localized copy. Keep names in a team directory, but make the role accountable when staff change. Where several companies collaborate, spell out each approval: a publisher's sign-off on a campaign does not necessarily mean the studio has cleared every captured scene for external use.
Restrict access to partner terms, budgets, unreleased announcements, candidate information and internal performance reports. They do not belong beside public screenshots in a broadly shared folder. Recheck permissions when a freelancer leaves or a publishing partnership changes. Folder labels help people work; access controls help prevent disclosure.
Use names that identify the asset without opening it
A filename should answer the team's usual retrieval questions in a consistent order. One possible pattern is Game_Campaign_Asset_Region_Language_Format_Version_Status. Harborlight_Launch_KeyArt_NA_enUS_1920x1080_v03_Approved.png tells a colleague more than new_banner_FINAL2.png. Small teams need not use every field every time, but they should agree on the ones they will use.
Define the terms first. Does v03 mean the third submitted design or the third approved one? Does Global include every territory? A brief naming guide can settle campaign names, region and language codes, and statuses. Avoid characters that cause problems in export tools, and keep filenames short enough to read in the team's usual file browser.
Status needs to match a real decision. Draft means editable work; InReview is awaiting a decision; Approved means the file can be used for a defined purpose. Renaming a file does not approve it. Keep the platform's version history where available, but include version numbers in filenames too: exports often leave the platform as email attachments.
Make the source-to-export relationship traceable
Design project files, raw gameplay captures and final exports serve different people. Keep a reference to exported versions alongside the source, or connect them in an asset index. If one key-art master produces store capsules, press images and event signage, nobody should have to guess which master was used by checking modification dates. A short text note can list fonts, plug-ins or linked artwork needed to reopen the file.
Track permissions and limits with the asset
A filename cannot hold every condition attached to a public-facing asset. Use an asset register—a spreadsheet or digital asset manager—to record its location, owner, approval date, intended channels, permitted markets, language, expiry or review date, and restrictions. Point the register to the file; do not turn it into another place for competing uploads.
Those restrictions can matter a great deal. A gameplay clip may show a feature later cut. Licensed music might be cleared for a launch video but not a booth loop. A creator's likeness or partner logo may need separate approval. Age-rating badges must match the territory and the material where they appear; promotional copy must not suggest that a pending rating has been granted. Put these conditions in the asset record and the handoff brief, not just in someone's memory.
Localization adds more decisions. Store descriptions, subtitles and screenshots may receive approval on different dates. Link each export to its language-specific copy and record who signed it off. A regional version may also need changes beyond the text in a graphic: platform requirements, dates, prices and depicted features can differ.
Make handoffs safe for publishers, press and event partners
An external request calls for a selected package, not access to the working drive. A publisher assessing a pitch may need the current deck, a short gameplay reel, screenshots, a fact sheet and a contact. An event organizer may need a logo, speaker portrait, session description and display artwork in specified dimensions. Include only what that recipient needs, plus a note with the game title, package date and permitted use.
Before sending it, open every file and test the links and permissions as someone outside the studio would. Remove tracked changes and internal comments. Set an access end date for confidential previews if the storage system allows it. If the recipient needs to pass files to regional teams, say whether that is permitted and whether filenames and approval notes must stay with them.
Event schedules make this especially important. A booth supplier might need print-ready files weeks before the trailer is final, while a meeting deck could change on the morning of an appointment. Use separate, clearly dated packages. Replacing a file in a shared folder does not update someone's earlier download; when an approved asset is withdrawn or replaced, send a short change note.
Build a workflow that prevents parallel versions
Duplicate files multiply when every reviewer downloads a copy, edits it and uploads it again. Choose one working location per deliverable and specify who may edit there. Direct comments and review requests to that location. If teams use different systems, name the source of truth and agree on when files move between them.
A simple asset path looks like this:
- Request: record the deliverable, channel, audience, dimensions, language, deadline and decision-maker.
- Create: keep source files and drafts in the campaign's working area.
- Review: gather feedback on one identified version and resolve conflicting comments before the next export.
- Approve: record the approver, permitted use and date, then place the export in the approved area.
- Distribute: share a recipient-specific package and record who received it if withdrawal may later be necessary.
- Retire: move superseded files out of the default browsing path while retaining what the team must keep.
Not every social post needs a committee. Match the checks to the risk. A small crop of approved art may only need a quick brand review; an unreleased character reveal or territory-specific rating claim warrants closer sign-off. Colleagues should be able to tell which process applies without digging through old chats.
Keep search useful as the library grows
Folders and filenames do most of the work, but tags help when a file serves several purposes. A gameplay clip could belong to a combat feature, a publisher pitch and a regional launch. Shared tags such as gameplay, vertical-slice and press-cleared work better than everyone's personal variations. Start with a small set and revise it as the portfolio changes.
Search results also need useful previews. Generate thumbnails for common formats where possible, and add a short description to records for files that are hard to preview. For video, note duration, aspect ratio, language and audio clearance. For documents, record the project and version; for design files, point non-designers to the export they should use.
Look for friction in everyday requests rather than creating a reporting project. Are people repeatedly asking for assets that supposedly have a home? Has outdated creative been sent? How long does a standard partner kit take to assemble? If approved screenshots remain hard to find, fix the path or index before writing more rules.
Archive without erasing useful history
A current logo should appear ahead of an old launch-day social crop. Move completed campaigns into dated archives and label retired assets so they cannot be mistaken for current approvals. Keep enough context to show what ran, where and when, especially for questions about previous market launches.
Set retention rules according to contracts, privacy obligations and legal advice. Cheap storage is no reason to keep sensitive exports forever. At the same time, deleting every source file after a campaign can make a new platform format expensive to produce. Decide which masters, final deliverables, approvals and performance records still have value, and who can authorize deletion.
When a contractor leaves, check the archive from a colleague's account. Fonts, cloud documents and design libraries may still depend on the contractor's personal workspace. Transfer ownership and test those dependencies; a copied folder may not contain everything needed to reopen the work.
Introduce the system without stopping production
Pilot the rules on one active campaign: agree on a folder map, naming pattern, approvers and asset register. Then give realistic retrieval tasks to the people who use the files—designers, community managers, publishing contacts and event staff. Can they find the current logo without messaging its creator? Can they tell whether a trailer is cleared for a conference presentation? Adjust the structure where they hesitate.
After the pilot, assign someone to maintain the shared rules and review them after major launches or staffing changes. Give new hires the folder guide with their permissions, including an example of a correctly filed source and export. For the next partner request, make a dated package named for the recipient and check it through an external-access test account before it goes out.
