export const meta = { title: "Guide to VFX Frame Handle Requirements for Plate Pulls", description: "Explains how many VFX plate handles to request, when to increase them, how to brief editorial, and how to confirm exported plates include the promised frame ranges.", tldr: "Define handles per shot, choose the show default or a per-shot override, then confirm delivered ranges against the cut. Use 8 frames each way as the minimum baseline, expand for retimes or difficult motion, and deliver a turnover sheet showing cut frames, plate range, and shortages.", slug: "guide-to-vfx-frame-handle-requirements-for-plate-pulls", publishedAt: "2026-09-12", readingTime: 9, thumbnail: "https://cdn.aspectlabs.dev/blog/guide-to-vfx-frame-handle-requirements-for-plate-pulls/cover-711d9a9e44eb.png", authors: ["gurish"], primaryTopic: "post-production", topics: ["post-production"], tags: ["vfx-handoff"], faq: [ { "question": "How many handle frames should I request for a standard VFX plate pull?", "answer": "If there's no show-specific spec, 8 frames at the head and 8 frames at the tail is a practical default for many VFX turnovers. Increase that amount for shots involving stabilization, retiming, tracking, paint, roto, complex camera movement, transitions, or likely editorial changes." }, { "question": "Does “8-frame handles” mean 8 frames total or 8 frames on each side?", "answer": "In most VFX turnover workflows, “8-frame handles” means 8 extra source frames before the first cut frame and 8 extra source frames after the last cut frame. Because different teams and tools may describe handles differently, the turnover spec should state this clearly." }, { "question": "Why do retimed shots often need more than normal handles?", "answer": "Retimed shots can use source frames in ways that don't match the visible timeline duration. A 50-frame timeline event may be based on a much shorter, longer, reversed, frozen, or non-linear source range. For retimes, provide the source range, timeline range, reference movie, retime type, and guidance on whether the vendor should work from original-speed media, a baked retime, or both." }, { "question": "What should be included in a VFX pull list for handled plates?", "answer": "A useful pull list should identify the shot ID, source clip or reel, timeline in and out, source in and out when available, requested head and tail handles, plate format, framing mode, color notes, retime notes, destination vendor or department, and any warnings about source-limited handles." }, { "question": "What should I do if the source media does not have enough frames for the requested handles?", "answer": "Deliver the available range, but clearly report the shortage in the turnover data. For example, note “requested 8 head / 8 tail, delivered 0 head / 8 tail due to source start.” Don't silently shorten handles, because the vendor needs to know whether missing frames are intentional, unavailable, or the result of an export problem." }, { "question": "How should missing or shortened handles be communicated after a pull?", "answer": "Short handles should be recorded as part of the plate’s turnover data, not buried in an email thread. In Aspect, teams can attach structured fields such as requested handles, delivered handles, source-limit warnings, and retime notes as custom metadata." } ], } Without a show-specific spec, 8-frame handles on both the head and tail of every VFX plate are the practical starting point; increase the handle length for shots that need stabilization, retiming, paint, tracking, or edit flexibility. That's the sane default because it's small enough not to explode your turnover size, but large enough to cover the most common conform and comp needs. Everyone needs to agree what the number means, because “8-frame handles” should mean 8 extra source frames before the first cut frame and 8 extra source frames after the last cut frame, not 8 total. Some pull systems and [CSV formats](https://partnerhelp.netflixstudios.com/hc/en-us/articles/51477329357715-VFX-Media-Submission-Tool-Library-User-Guide) define handles exactly this way: an integer value added to both the front and tail of the clip. Your team should resolve different language in the turnover notes before plates go out. Handles are cheap when you plan them early, but they get expensive when the vendor discovers missing frames after a comp is built, a camera solve is approved, or a paint task is already in progress. ## Why VFX vendors ask for handles A plate pull is a technical source package for work that has to survive notes, revisions, and reintegration into the edit. The visible cut frames are only the center of the problem. VFX artists use extra frames for a few common reasons: - A stabilized shot often needs frames outside the edit to smooth motion into and out of the edit. - Trackers may need more motion before or after the selected edit to get a reliable solve. - A roto shape, patch, or clean plate may need to be built before the first used frame so the result is already stable at the edit point. - If editorial used a speed effect, the vendor may need source frames that aren't obvious from the edit duration. - If the edit slips by a few frames, a handled render can often be reused instead of repulled. The takeaway is simple: handles are working material. Without them, the vendor may have to fake motion, freeze frames, rebuild missing edges, or ask editorial for a new pull. ## The default handle length is a workflow decision There's no universal handle length that fits every production. Some student or tightly controlled workflows turn over exact cut length plates by default and only add handles when requested. Larger episodic, feature, commercial, and streaming workflows often expect handles as part of the standard VFX pull. Both approaches can work, but they require different discipline. If the edit is locked, the work is simple, and the vendor has confirmed [no handles](https://fsufilmhandbook.com/turnover-to-vfx/) are needed, exact-length plates are fine. That usually applies to very simple screen inserts, static monitor replacements, or isolated graphics work where the visible cut frames are all that matter. For most professional turnovers, though, no handles should be the exception. A few extra frames on a 40-frame shot aren't a big storage problem. A missing frame range on a high-priority shot during finishing is. A good handle policy accounts for three constraints: shot method, editorial status, and source availability. Technically complex shots need more handles. Edits that are still moving need more handles. Source clips that begin or end near the edit point need a note that the pull couldn't fully supply the requested handle. ## Standard handle lengths by shot type Use these ranges as a starting point, then replace them with the show spec when one exists. The numbers assume the pull adds handles on both the head and tail. | Shot type | Suggested handles | Why | |---|---:|---| | Simple screen insert or graphic comp | 8 frames | Enough for minor slips and cut reintegration | | Basic paint, cleanup, or object removal | 8 to 12 frames | Gives paint and roto time to settle across edits | | Green screen or bluescreen key | 8 to 16 frames | Supports edge work, garbage mattes, and continuity | | Camera tracking or matchmove | 12 to 24 frames | Extra motion can improve track stability | | Stabilized or reframed plate | 16 to 24 frames | Smooths motion and protects against edge reveal | | Retimed shot or speed ramp | 24 frames or more | Source-frame needs may exceed visible cut duration | | Dissolve, transition, or optical overlap | Cover the full overlap plus handles | The visible contribution extends beyond the event boundary | | Heavy simulation, CG integration, or complex comp | 16 to 32 frames | Gives downstream departments room for pre-roll and revisions | | Plate near source start or source end | As much as available | Your team must call out missing handles clearly | These are negotiation values. A vendor may ask for 12-frame handles as a show standard, while a supervisor may request 24 or 32 on specific shots. The key is to avoid silently applying one handle rule to every shot when the work clearly varies. For long-form work, many teams settle on one default handle length for the show, then allow per-shot overrides. That keeps pull lists manageable while still supporting special cases. ## Handles are only one kind of protection Frame handles protect time, but they don't protect framing. This distinction matters because many VFX problems are caused by confusing the two. If a shot needs stabilization or repositioning, the vendor may need [extra frames and extra image area](https://www.youtube.com/watch?v=V0pRmGGmdT4). Handles help with the motion over time. Overscan, full-frame extraction, or a safe-area framing decision helps with the image edges. Camera and post workflow guidance for anamorphic and large-format projects often talks about [preserving a protection area](https://www.arri.com/resource/blob/388830/8e291fd59589918e30d20677af9f0290/arri-alexa-35-anamorphic-formats-in-post-production-workflow-guideline-data.pdf) for stabilization and repositioning. In one common pattern, the finishing frame is derived from a larger captured image, and the VFX plate includes extra image area so the vendor can work without immediately hitting the raster edge. For an anamorphic show, that may involve a specific desqueeze, extraction, and safe-area decision. For spherical footage, it may mean full sensor, full aperture, or a padded framing mode rather than the edit crop. When you communicate handle requirements, communicate framing requirements at the same time. A plate with 24-frame handles but the wrong crop can still be unusable for stabilization. A full-frame plate with no handles can still fail if the edit slips. ## Retimes need special attention Retimed shots are where handle assumptions break fastest. A timeline event may be 50 frames long, but the source frames used to create it might span 20 frames, 200 frames, or a non-linear range depending on the effect. If the speed effect is baked into a reference QuickTime but the vendor receives only the visible source range with default handles, they may not be able to reproduce the motion. For retimed shots, send the vendor enough information to understand both the editorial intent and the source frame usage: - The retime type: constant speed, speed ramp, reverse, freeze, timewarp, or blended effect. - The visible cut range in timeline timecode. - The source clip range used by the retime, including any available extra frames. - A reference movie with burned-in timecode and shot name. - Whether the vendor should work on the original-speed plate, a baked retimed plate, or both. The safest approach depends on the shot. For a simple constant-speed shot, the vendor may prefer original-speed plates plus a reference. For a complex editorial timewarp, they may need a baked element for comparison or comp timing. Either way, default handles alone aren't enough information. ## How to communicate handle requirements to editorial The best handle request names the exact handles to add, is explicit, and machine-readable. Editorial shouldn't have to infer technical requirements from a note like “add handles where needed.” That creates inconsistent pulls and forces the assistant editor to become the decision point for every VFX method. A useful turnover request usually includes these fields: - Shot ID or VFX ID - Source clip name or reel - Timeline in and out - Source in and out, if available - Requested head handle - Requested tail handle - Plate format, such as EXR sequence, DPX sequence, or QuickTime - Framing mode, such as full frame, extraction, UHD, HD, or overscan - Color pipeline notes - Retime notes - Vendor or department destination - Any known source-limit warnings This information can live in an EDL, CSV, spreadsheet, database export, or pull tool. The format matters less than the clarity. Some systems let a deliverable act like a reusable recipe that defines format, start frame, handles, and framing. Others let each row in a CSV drive the handle count and output configuration. That's ideal when [different marker colors](https://vfxtoolbox.fcp.cafe/how-to-use/), shot types, or vendors need different settings. Aspect gives editorial, finishing, and VFX one shared cloud location for turnover assets and pull sheets. That keeps plates, references, and handle notes together instead of scattered across duplicate uploads and handoff folders. If your workflow supports per-event deliverables, your team should use them. A green marker could mean standard EXR plates with 8-frame handles. A blue marker could mean full-frame EXR with 24-frame handles. A yellow marker could mean retime review with a baked QuickTime reference. The goal is to remove guesswork from the person doing the pull. ## Where handle mistakes usually happen Most handle problems happen because the pull path is more complicated than the visible edit. Common failure modes include: - The requested handle count was added to the timeline event, but the source media didn't have enough frames. - A nested sequence, compound clip, multicam angle, or collapsed effect hid the true source clip. - A retime was treated like a normal-speed event. - The plate was exported from a cropped or resized timeline instead of the agreed source framing. - The vendor expected handles on both sides, while editorial interpreted the number as total extra frames. Build a [pull workflow](https://movielabs.com/prodtech/case-studies/MovieLabs_Sony_Case_Study.pdf) that exposes these cases. Your pull prep should reveal nested media, speed effects, transitions, and source-boundary warnings before upload. ## Verifying handles during the pull Your team should verify handles while preparing the plates. The assistant editor, VFX editor, or finishing/pulls editor should be able to confirm three things for every plate: the cut range, the delivered range, and the available source range. | Plate or case | Range to confirm | Inspection method | Clean result | |---|---|---|---| | Image sequence | Delivered frame count equals cut duration plus head and tail handles | Count files and spot-check the first frame, first cut frame, last cut frame, and last frame in a frame-aware viewer | The sequence contains the expected number of files and the cut frames are clearly identified | | QuickTime plate | Duration, burn-in, first visible frame, and last visible frame | Open the file in a player or NLE that displays timecode and frame stepping | The file duration matches the requested handled range and the burn-in agrees with the [turnover sheet](https://workflow.deganz.co.nz/wp-content/uploads/2020/08/PRPP_Guide_to_VFXHandovers_v0.4_20200222.pdf) | | Retimed shot | Source range used by the retime and any baked timing reference | Compare the plate, retime notes, and reference movie with burn-in | The vendor can identify original-speed source frames and editorial timing | | Source-limited shot | Requested handles compared with delivered handles | Compare source start and end against requested head and tail frames | Any missing head or tail frames are named in the turnover data | For example, if a shot is cut from source timecode 01:12:10:00 to 01:12:12:00 at 24 fps, and the request is 8-frame handles, the delivered source range should begin at 01:12:09:16 and end at 01:12:12:08, assuming your tools handle inclusive/exclusive frame conventions consistently. The exact counting convention should match your facility workflow, but the math should be explainable. For [image sequences](https://movielabs.com/prodtech/sdw/vfx/ETC-ImageSequenceNaming-v1.0-063020-FINAL.pdf), verify the frame count against the expected cut duration plus head and tail handles. A 40-frame shot with 8-frame handles on both sides should deliver 56 frames, unless one side is source-limited. If the sequence starts at frame 1001, that would typically run 1001 through 1056 when counted inclusively as 56 image files. If your facility uses a different start frame convention, document it and keep it consistent. For QuickTime plates, open the file and inspect the duration, burned-in timecode, and first and last visible frames. QuickTimes are easier to skim, but easier to misread if there's no burn-in. For EXR or DPX, spot-check the first frame, first cut frame, last cut frame, and last frame in a viewer that shows frame numbers and metadata. Aspect streams media to Finder or your NLE, so an assistant can spot-check heavy EXR, DPX, or source media without waiting on a full download. The plate opens from the shared cloud location while verification is still happening. The notes that travel with the plate should make verification possible without opening the edit timeline. If the vendor sees a plate range, cut range, and handle count in the turnover sheet, they can confirm receipt quickly and flag missing material right away. ## Naming and frame ranges should make handles obvious A plate can technically contain handles and still be confusing. If the file sequence starts at 1001 but nobody identifies which frame is the first cut frame, the vendor has to reverse-engineer the edit. That wastes time and creates avoidable mistakes. There are two common patterns. One is to start every plate sequence at a standard frame like 1001 and identify the cut-in frame in metadata or a turnover sheet. The other is to preserve source frame or timecode-derived numbering so the image sequence maps directly to the camera source. Both can work, but what matters is consistency across the show and clarity in the pull list. For handled plates, include enough context to answer these questions: - Which delivered frame is the first frame used in the cut? - Which delivered frame is the last frame used in the cut? - How many handle frames are present at the head and tail? - Was either handle shortened because the source ran out? - Does the reference movie show the cut length only, the handled length, or both? Don't assume the vendor will know your facility’s convention. Spell it out once in the turnover spec, then keep every pull aligned to that spec. ## When to ask for more than the default Some shots deserve extra handles even if the show default is 8 or 12. The earlier you identify them, the less repulling you'll do. Increase handles when editorial is still testing cut points around the shot, or when the shot has conditions that make short handles risky: - unstable handheld motion, a long lens with drift, or a whip pan - a complex camera move, foreground occlusions, or heavy roto - water, smoke, or crowds - hair - practical interactive light that needs temporal analysis Ask the vendor before increasing handles across an entire sequence. More frames mean more storage, longer uploads, longer conform time, and more frames that may enter tracking, roto, simulation, or review by accident. A 24-frame handle policy on a few hard shots is smart, but a 24-frame policy on hundreds of simple shots may just create noise. ## What to do when handles are unavailable Sometimes the source clip doesn't have the requested handles. The camera may have cut immediately before action, the slate may start too close to the edit, or the selected take may end at the exact moment editorial needs. In that case, don't silently deliver shorter handles and hope nobody notices. Call out the shortage in the turnover data. Use plain language like “requested 8 head / 8 tail, delivered 0 head / 8 tail due to source start.” Your team should mention any alternate take, longer source range, clean plate, or adjacent timeline media that might help. The vendor may still be able to work. They might hold a frame, create a clean plate, extend the edge, use adjacent frames, or request a different source. What they can't do efficiently is guess whether missing handles are intentional. ## The cleanest handoff is a shared spec A good VFX handle workflow relies on a shared spec that editorial, post supervision, finishing, and vendors all understand. That spec should define the shared decisions your team will use during pulls: - the default handle length and per-shot override rules - frame numbering convention - plate format and framing policy - color pipeline and retime handling - how your team reports source-limited handles For most shows, the working rule is straightforward: use 8-frame handles as the minimum default, raise the count for shots with motion or timing complexity, communicate the requirement per shot, and verify the delivered frame range against the cut range before the vendor starts work. Do that consistently and handles stop being a recurring emergency.