The process from start to finish: what exactly to send to a game animation studio, where your feedback has the most impact, and which files you should expect at delivery.
Key takeaways
Game animation is runtime content, not a rendered video. It has to loop, blend and run within your engine’s limits.
A clear move list, source art and engine version prevent most animation rework.
A short test animation locks style and timing before full production starts.
Feedback works best when it matches the stage: timing at blocking, detail at polish, gameplay feel in engine.
Agree on file formats, naming and runtime versions before the first clip is exported.
Keeping art and animation with one studio reduces handoff problems between the two.
How we work as a game animation studio: the complete workflow
You have shortlisted three game animation studios, and every showreel looks strong. What a showreel cannot show is how a studio handles your files, your engine and your feedback once production starts. That is where most animation projects either run smoothly or start to slip.
Many studios that call themselves an animation studio work in film, TV or explainer video. Their workflow ends with a rendered clip. Game animation ends somewhere else: inside your build, running on your target device. This post walks through how Saigon Dragon Studios (SDS) works as a game animation studio, from the first brief to engine-ready files, so you know what to prepare and what to expect.
Game Animation Studio vs. General Animation Studio: Why the Workflow Differs
A game animation studio delivers files your engine plays in real time, not a finished video, and that changes every stage of the workflow.
In film or explainer animation, the final frame is the product. In games, an animation is one part of a system. It has to loop cleanly, hand over to the next state and stay readable at gameplay camera distance. It also has to fit the memory and performance budget of your target platform.
| Aspect | Film, TV or explainer animation | Game animation |
|---|---|---|
| Final output | A rendered video | Animation data your engine plays at runtime |
| Structure | One continuous sequence | Separate clips: loops, one-shots and transitions |
| Review | Watching the final cut | Checking clips in context, at gameplay speed |
| Technical limits | Mostly render time | Bone counts, file size, atlas size, frame budget |
| Success test | It looks right on screen | It looks right and plays right in the build |
That is why we treat technical questions as part of the creative brief. Building our own RTS, Space Tales, showed us how quickly rig limits and engine quirks decide what animation can deliver.
What SDS Animates: 2D Spine Animation, 3D Character Animation and VFX
SDS produces 2D and 3D game animation, including character animation and VFX animation, using tools such as Spine and Unity where the project calls for them.
On the 2D side, this typically means skeletal character animation in Spine and effects for gameplay and UI moments. On the 3D side, it means character animation for game-ready models, with rigging where relevant. SDS also produces 2D and 3D character art, so the same team can prepare art with animation in mind from the start.
That matters more than it sounds. A lot of animation rework comes from art that was never built to move: merged layers, missing hidden areas behind limbs, or meshes that deform badly at the joints. When art and animation stay with one production partner, these problems surface during concept, not after the files have changed hands. If you are scoping art and animation together, SDS can support both through one point of contact, either per project or as a dedicated team that works inside your pipeline.
What to Send a Game Animation Studio Before Production Starts
A complete animation brief covers source art, a move list, your engine and runtime versions, motion references and your technical limits.
The general rules for writing a game art outsourcing brief still apply. Animation adds a few items that are easy to leave out, and each one prevents a specific kind of rework.
| What to send | Why it matters |
|---|---|
| Source art | Layered files for 2D, or the model and any existing rig for 3D. This decides whether art can be rigged as it is or needs preparation first. |
| Move list with clip names | This defines the scope. Mark each clip as a loop or a one-shot, and note which clips need to transition into each other. |
| Engine, engine version and Spine runtime version | Exported Spine data needs to match the runtime your game uses. A mismatch late in production can mean re-exporting every file. |
| Motion references | Clips from games you like show the feel you want: snappy, weighty or bouncy. A word like “dynamic” means something different to every reader. |
| Technical limits | Bone counts, atlas size, file size or frame rate targets for your platform. |
| Naming conventions | Clip and file names that import without manual sorting. |
| Milestones and reviewers | When feedback can happen, and who gives the final sign-off. |
If your game uses a stylized art style, motion references matter even more. Stylized animation depends on exaggeration and timing choices that are hard to describe in writing and easy to misread.
How a Game Animation Project Moves Through Production at SDS
Most game animation projects follow the same order: brief review, art and rig preparation, a test animation, blocking, polish, and an export check before delivery.
The exact steps depend on whether the work is 2D or 3D, the type of asset and how your own pipeline is set up. The sequence below is the typical flow.
- Brief review and questions. We read the brief for gaps before work starts. Expect questions about engine version, clip transitions and platform limits. They are much cheaper to answer on day one than halfway through production.
- Art and rig preparation. For 2D, the artwork is split into parts and a skeleton is built in Spine. For 3D, the model is rigged, or an existing rig is checked against the move list. This is where deformation problems are caught.
- Test animation. One representative clip, such as an idle or a basic attack, is animated first. It locks timing, style and file setup before the full move list goes into production.
- Blocking. Key poses and timing are set without detailed in-betweens. This is the cheapest stage to change direction.
- Polish. Spacing, overlap, secondary motion and effects are added. Changing core timing now costs more, because detailed work has to be redone.
- Export and check. Clips are exported in the agreed format and checked for clean loops, transitions and naming before delivery.
The test animation also shows you what the collaboration feels like before you commit to a larger scope. SDS is a Ho Chi Minh City studio of 60+ artists working in five languages, with contributions to 100+ shipped games. If you want to know who you would be working with, meet the team behind the work.
How Feedback Works in Game Animation Reviews
Animation feedback is most effective when it matches the stage: poses and timing at blocking, detail at polish and gameplay feel at the final check.
| Stage | Focus your feedback on | Save for later |
|---|---|---|
| Test animation | Overall style, feel, speed and file setup | Small details that polish will fix |
| Blocking | Poses, timing, readability and silhouette | Secondary motion and effects |
| Polish | Overlap, follow-through, effects and small timing tweaks | Changing the core action |
| Export and check | Blending, speed at gameplay scale and hit timing | Reopening approved style decisions |
A few habits make reviews faster on both sides:
- Send one consolidated round of notes from one reviewer, not separate messages from several people.
- Point to frame numbers or timestamps instead of general impressions.
- Give the gameplay reason behind a note, for example that an attack needs to read before the hit window opens.
- Review clips at the camera distance players will actually see.
Feedback speed shapes the schedule as much as the scope does. Building review checkpoints into your milestone plan keeps animation from waiting on approvals. Agreeing on what “approved” means at each stage helps too, the same way it does in long-term production partnerships. SDS shares more practical guidance on briefs, reviews and technical specs on the studio blog.
What Engine-Ready Animation Files From a Game Animation Studio Include
Engine-ready means your files import without rework: the agreed format, the right runtime version, consistent names and clean loops.
| Deliverable | 2D Spine animation | 3D animation |
|---|---|---|
| Animation data | Exported skeleton data (JSON or binary) | Animation clips, often as FBX, unless agreed otherwise |
| Textures | Texture atlas and atlas page images | Uses the textures from the model’s material setup |
| Clip structure | Named animations within one skeleton | Clips named and split per your conventions |
| Movement setup | Events and loops set up as agreed | Root motion or in-place, as agreed in the brief |
| Source files | Spine project files, if included in scope | Source scene files, if included in scope |
Source file delivery, frame ranges and root motion setup belong in the brief, not in a discussion at delivery. For 3D work, the same logic applies as with 3D modeling specs that match your game engine.
Your Next Step: Prepare Your Animation Brief for a Game Animation Studio
Before you contact any game animation studio, put three things together: your move list, your source art and your engine and runtime versions. With those in hand, a studio can give you a realistic answer instead of a generic quote.
If you want a production partner that handles art and animation together, get in touch with Saigon Dragon Studios and tell us where your project stands. We will come back with specific questions about your animation, not a standard pitch.
References & data sources
- Saigon Dragon Studios company profile and services: SDS internal content strategy and saigondragonstudios.com.
- Esoteric Software, Spine User Guide (export formats, texture packing) and Spine Runtimes documentation (editor and runtime version compatibility). Confirm current wording before publishing.
- No external statistics or figures are used in this post.
A game animation studio creates character, creature, UI and VFX animation that runs inside a game engine. Unlike film animation, the output is animation data and clips rather than a rendered video. The work has to loop, blend between states and stay within your platform’s performance limits.
Send your source art, a move list with clip names, your engine and version, and motion references. For 2D Spine work, include your Spine runtime version. Technical limits such as bone counts or atlas size help the studio give an accurate estimate.
Spine animation uses 2D artwork split into parts and moved with a skeleton, which keeps file sizes small and suits many mobile and stylized games. 3D animation drives a rigged 3D model. The right choice depends on your art style, platform and engine.
Revisions are usually tied to production stages such as blocking and polish. Changes are cheapest at blocking, when only key poses and timing exist. The number of revision rounds depends on the agreed scope, so it is best defined in the brief.
For Spine projects, delivery typically includes exported skeleton data in JSON or binary format plus a texture atlas. For 3D, animation clips are often delivered as FBX. Whether source files are included should be agreed before production starts.
