To turn engineering CAD into an accurate product animation, a marketing team needs five things from engineering: the assembly at a named revision (native files or a STEP AP242 export), a parts list marking what may be shown, finish callouts for every visible part, the motion limits of anything that moves, and named reviewers for accuracy and release. CAD file rendering rarely fails at the render. It fails at the handoff: wrong units, missing finishes, or internal parts nobody cleared for public view.
This guide sets out what to ask for, the checks to run on the files, and who signs each one off. For defense, space and other export-controlled products it adds the step most guides skip: a render can carry the same information as a drawing, so your export-compliance team, and your contracts team where a contract requires it, reviews the frames before anything is posted or shown.
What engineering must hand over for CAD file rendering
The handoff is a package, not a file. The geometry matters most, but the animation also needs to know which parts it may show, what each surface looks like, how the parts move, and who decides whether the result is accurate and releasable. Ask for all of it in one request so engineering can answer it once.
| Item | What it is | Why the animation needs it | Usually supplied by |
|---|---|---|---|
| Assembly at a named revision | Native CAD or a STEP export, with revision letter and date | Exact geometry and proportions; ties every frame to a drawing | Design engineering |
| Visibility list | The parts list (bill of materials) with each part marked show, simplify or hide | Decides what is modeled, what is replaced by a simple shape and what is removed | Engineering with product marketing |
| Finish callouts | Color reference, gloss, texture, coatings, transparent parts, markings | Look development: the render has to match the product on the shelf | Industrial design or product management |
| Physical sample or reference photos | A production or pre-production unit, photographed under neutral light | The only way to check the finish callouts against reality | Product team |
| Motion data | Hinge axes, travel limits, the order parts come apart, speeds that will be shown | Correct movement in exploded views and mechanism shots | Engineering |
| Release status | Which parts, views, numbers and labels may be public | The posting decision | Export compliance, communications, contracts |
| Reviewer names | Who checks accuracy, brand look and release, and how long each needs | Sign-off dates in the schedule | Marketing lead |
Every file that arrives goes into an input register: file name, revision, date received, the person who sent it, and the use it was released for. The register answers the question reviewers ask at the end (“what was this built from?”) and it is the record that keeps a later engineering change from slipping silently into a finished film.
Two items are often missing from the first request. The first is the visibility list. Without it, the studio either models parts nobody needs (costing time) or shows parts nobody cleared (costing a review cycle, or worse). The second is reviewer time. An engineering accuracy check on a greycard can take a day or a week depending on who does it, and the schedule should use your number, not a guess.
Native CAD, STEP or a mesh: which files to ask for
Ask for a STEP AP242 export of the full assembly as the working file, plus the native files only if the studio runs the same CAD system and your policy allows them to leave the building. Accept a mesh export only when it is the only thing released, and then ask for the tolerance it was exported at.
Native files
Native files are what your engineers work in. They hold exact surfaces, the feature history and often the assembly constraints. They open reliably only in the CAD system that wrote them, or through a translator, and they carry more design intent than an animation needs: dimensions, tolerances, sketches and sometimes supplier part numbers. For a marketing film that extra content is a release question, not a benefit.
STEP AP242
STEP is the ISO 10303 family of standards for exchanging product data. The Library of Congress format description explains that the STEP-file (ISO 10303-21) is a plain-text exchange structure that is “typically used as a middle-state format for exchange between systems operated by different parties”. The data inside follows an application protocol. AP203 has been used mainly in aerospace and defense and AP214 mainly in automotive; AP242, “Managed model-based 3D engineering”, was developed to combine and extend both, was first published in 2014, and a 2025 edition was published by ISO.
For animation, the useful part of a STEP export is that it keeps exact surfaces, so the studio can tessellate each part at the precision its shots need. Depending on the exporter settings, it can also carry the assembly structure, part names and colors. Ask engineering to send one small sample export first, and check that the hierarchy and names survive before the full handoff.
Meshes
A mesh export (STL, OBJ and similar) has already been converted to triangles. The Library of Congress describes STL as a format “for describing the surface of an object as a triangular mesh” and notes that it has “no standard support within STL for colors or textures” (LoC, STL format family). A mesh made for 3D printing or simulation may be far coarser or far denser than a camera needs, and the exact surfaces cannot be recovered from it.
| Source file | Holds exact surfaces | Keeps assembly and names | Main risk for animation | Ask for it when |
|---|---|---|---|---|
| Native CAD | Yes | Yes | Carries design detail the film does not need | The studio runs the same CAD and your policy allows it |
| STEP AP242 | Yes | Usually, depending on export settings | Hierarchy, names or colors lost in export | Almost always: this is the working file |
| Mesh (STL, OBJ) | No | Rarely | Tessellated at someone else’s tolerance | It is the only thing released for this use |
A practical rule: whichever format you send, the revision letter goes in the file name and the input register. If engineering issues revision D while the studio animates revision C, the register shows which shots are affected.
Tessellation and decimation: from exact surfaces to triangles
Animation and rendering software generally works with polygon meshes rather than CAD’s exact surfaces, so each part is converted to triangles at some point. The tolerance of that conversion decides whether a curved edge looks smooth in a close-up or shows flat facets.
The glTF 2.0 specification from the Khronos Group shows the constraint plainly: geometry is stored as points, lines or triangles (glTF 2.0 specification). There is no place in it for an exact curved surface. The Library of Congress uses the same word for the process: breaking a surface into small triangles is “tessellation”.
The two controls
CAD exporters usually express tessellation as a distance and an angle. Autodesk’s help for its Inventor STL export, as one tool maker’s example, defines surface deviation as “the maximum distance between the facet edges and the surface edges” and normal deviation as “the maximum angle between the normal vectors of the facets”. It also warns that “a tolerance setting that is too tight can result in excessive facets and depletion of memory”, in which case the export can fail (Autodesk Inventor help, STL options). Other CAD systems use different names for the same two ideas.
The distance control (often called chord height or chordal deviation) is the one that shows in a silhouette. Smooth shading hides facets on the face of a surface, because the renderer blends the normals across triangles, but the outline of a curved edge is drawn by the triangles themselves.
A worked check on one round edge
Suppose a product has a round housing with a 40 mm radius, and one shot fills a 2160-pixel-tall 4K frame with its full 80 mm diameter. That is 2160 / 80 = 27 pixels per millimeter. The chord height of each straight segment is s = r x (1 - cos(half the segment angle)):
| Segments around the edge | Angle per segment | Chord height s | On screen (s x 27 px per mm) |
|---|---|---|---|
| 16 | 22.5 degrees | 40 x (1 - cos 11.25) = 0.77 mm | About 21 px: clearly faceted |
| 64 | 5.625 degrees | 40 x (1 - cos 2.8125) = 0.048 mm | About 1.3 px: at the edge of visibility |
| 256 | 1.40625 degrees | 40 x (1 - cos 0.703125) = 0.003 mm | About 0.08 px: invisible |
The table explains a common surprise. A model that looked fine in a wide shot shows a polygonal outline the moment the camera pushes in. The fix is not to tessellate everything finely, which inflates file size and render time. It is to tessellate each part to the closest framing it gets.
Tessellate per part, by camera distance
A workable rule is three tiers, written into the plan:
- Hero parts that fill the frame in a close-up: fine tolerance, checked in the actual close-up framing at delivery resolution.
- Visible parts in mid and wide shots: a standard tolerance that keeps the silhouette clean at their largest size on screen.
- Hidden or blocked parts: coarse, replaced by a simple shape, or removed. Fasteners that repeat are modeled once and instanced.
Decimation is a separate job
Decimation reduces the triangle count of a mesh that already exists. It belongs to real-time deliverables, such as a glTF model for a product page viewer, where file size matters more than a perfect close-up. Keep the render mesh and the real-time mesh as separate files with their own names. A decimated mesh that ends up in a hero close-up is a frequent cause of a late reshoot of the render.
Units, scale and orientation: the silent errors
Check units and up axis before any look development, because both errors are silent. Nothing crashes. The model arrives a thousand times too large, or lying on its side, and the first person to notice is the lighter wondering why the shadows look wrong.
Formats disagree on defaults. The glTF 2.0 specification says “the units for all linear distances are meters” and that glTF “defines +Y as up”. OpenUSD stores a stage’s units as meters per unit and, if none is authored, falls back to 0.01, that is centimeters (OpenUSD, UsdGeom linear units). Its up axis is configurable, “either +Y (the fallback) or +Z” (OpenUSD rendering guide). A part modeled in millimeters in CAD therefore has to be scaled on its way into either format.
Suppose a part is 250 mm tall and its coordinates are copied across as raw numbers, without conversion:
- In glTF, 250 units are read as 250 meters.
- In a USD stage with no authored units, 250 units x 0.01 meters per unit = 2.5 meters.
- Correctly converted, it is 0.25 meters in glTF, or 25 units in a centimeter USD stage (25 x 0.01 = 0.25 meters).
Scale matters beyond appearance. Depth of field, the falloff of lights placed near the product, and any simulation (liquid, cloth, particles) behave according to size, so a bottle at 2.5 meters looks like a building.
The dimension check
Make a simple test part of every handoff: pick three dimensions from the released drawing (an overall height, a hole spacing, a wall thickness that will be visible in a cutaway) and measure them in the render scene. Record the three numbers and who checked them in the input register. It takes minutes and it settles the question before any review.
Pivots and axes
Parts that move need their pivot at the real hinge axis. CAD assembly constraints often hold that information, but a STEP export or mesh may not. Ask engineering for the axis positions and travel limits of every moving part in the film: lid hinge, trigger, latch, deploying panel. A door that swings around its own center instead of its hinge reads as wrong to every engineer who watches.
Materials and finishes: what the callouts must say
A CAD material assignment describes engineering properties (an alloy grade, a density), not how the surface looks. The finish callout is a separate document, and it is the one look development works from.
Rendering formats describe appearance with physically based parameters. glTF “uses the metallic-roughness material model”, with base color, metallic and roughness values, and the Khronos Group lists further effects carried in extensions, among them clearcoat, transmission, index of refraction, sheen, iridescence and anisotropy (Khronos, glTF). None of those values can be read off a CAD file. Someone has to say what the product looks like.
| Callout | What to write | What the 3D artist sets from it |
|---|---|---|
| Color | The brand’s color reference for each part, plus a physical chip or production sample | Base color, checked against the sample under neutral light |
| Gloss | Matte, satin or gloss, or a measured gloss value if your quality team records one | Roughness |
| Texture | Bead-blast, brushed (with grain direction), knurled, textured plastic (with the texture reference) | Roughness and normal maps |
| Coating | Anodize, powder coat, clear coat, plating | Clearcoat, metallic values, color shift at angles |
| Transparent parts | Lens, window or light pipe: material, tint and frosting | Transmission and index of refraction |
| Markings | Logos, regulatory labels, rating plates, as artwork files | Decals placed to the drawing |
| Colorways | Every color the product ships in | Material variants |
Two items deserve care. Markings first: a rating plate or regulatory label in a close-up is read by viewers, so it uses the current approved artwork, and serial numbers, lot codes and other unit-specific data are replaced with neutral placeholders. Colorways second: glTF has a material variants extension, developed with the Khronos 3D Commerce working group, which lets one file carry several colorways (Khronos, glTF), so a launch with five colors does not need five copies of the geometry.
The physical sample is the final reference. Photograph it beside a gray card under daylight-balanced light, and keep those photos with the finish callouts. Look development is then a comparison: render and photograph side by side, adjusted until a product manager who handles the real unit every day signs that they match. For color fidelity in real-time viewers, the Khronos Group publishes a PBR Neutral tone mapper designed for faithful reproduction of a product’s base color, hue and saturation.
Assemblies for exploded views and cutaways
An exploded view or cutaway shows how a product is built, so it needs the assembly structure, a deliberate order of movement, and a decision about every internal part. Get those three from engineering before the greycard, not after.
From assembly tree to animation groups
The CAD assembly tree becomes the animation hierarchy. Subassemblies that move together (a lid with its gasket and hinge pin, a battery with its latch) should arrive as named groups. If the export flattens everything into one list of anonymous bodies, the studio has to rebuild the groups by hand, and every rebuild is a chance to put a part in the wrong group.
The order parts come apart
The explode order is a creative decision with an engineering constraint. Parts should separate along paths they could physically travel, in an order that makes sense for the product: covers before what they cover, fasteners before the parts they hold. Engineering confirms the order on the greycard, where a change costs minutes. The same change after final materials and lighting costs a full re-render of the shot.
Internal parts and cutaways
A cutaway or a separating housing exposes what is inside, and that is where accuracy and release meet. Every internal part in the shot needs one of three decisions from the visibility list: show it as designed, replace it with a simplified shape that conveys the principle, or hide it. Simplified geometry often explains a product just as well and keeps design detail out of the frame. For a medical device, the internal mechanism may also be the product’s claim, which brings regulatory review into the same shot (see mechanism of action animation for medical devices).
Example (fictional). Orlenna is an invented Colorado bottle brand and the Ridge Bottle is not a real product; every figure is an illustration from Blendpipe’s example campaign. Shot 4 of the 30-second hero spot, “Inside the wall” (12 to 17 seconds), is a 3D exploded view built from the product drawings: the wall separates into outer steel, vacuum gap, copper lining and inner steel. The visibility list marks the lid’s internal seal as hidden, because the shot is about the wall. The explode order is outermost layer first, so viewers move inward toward the vacuum gap. The shot is 5 seconds at 24 fps, or 5 x 24 = 120 frames, part of the spot’s 11 seconds of 3D. The render shows how the bottle is built; the claim “twelve hours hot” needs the brand’s own test evidence, which the render illustrates rather than proves.
Export control and public release: the check before anything is posted
If the product is, or contains, a defense article or an export-controlled item, a render can carry the same information as a drawing or photograph. Your export-compliance team decides what may be shown, where and to whom, and your contracts team decides whether a contract clause requires the customer’s approval first. This section describes what the regulations say so you can plan the review; it is not legal advice.
What a frame can reveal
The ITAR, which the State Department administers through its Directorate of Defense Trade Controls (22 CFR 120.1), defines technical data to include information “required for the design, development, production, manufacture, assembly, operation, repair, testing, maintenance, or modification of defense articles”, including “blueprints, drawings, photographs, plans, instructions, or documentation” (22 CFR 120.33). The same section excludes information in the public domain and “basic marketing information on function or purpose or general system descriptions of defense articles”.
That pair of sentences is the planning brief for a defense product animation. A film that explains what a system does and roughly how it is arranged is working in the territory the definition excludes. An exploded view at engineering precision, a cutaway that shows internal layout, or on-screen performance figures may not be. Where the line falls for a given product is your export-compliance team’s decision, and only they can make it.
Public domain and published information
The ITAR defines public domain as information “which is published and which is generally accessible or available to the public”, through listed routes (22 CFR 120.34). Two matter for marketing:
- “unlimited distribution at a conference, meeting, seminar, trade show, or exhibition, generally accessible to the public, in the United States”
- “public release (i.e., unlimited distribution) in any form … after approval by the cognizant U.S. Government department or agency”, which cross-refers to the exemption in 22 CFR 125.4(b)(13) for technical data approved for public release
The Export Administration Regulations take a similar approach for dual-use items. Published information is not subject to the EAR (15 CFR 734.3(b)(3)), and information is published when it has been “made available to the public without restrictions upon its further dissemination”, for example through “unlimited distribution at a conference, meeting, seminar, trade show, or exhibition, generally accessible to the interested public” or “posting on the Internet on sites available to the public” (15 CFR 734.7). Note one difference in wording: the ITAR trade-show route says “in the United States”, and the EAR route does not.
Whether a particular frame is already public, whether posting it would itself be a release, and which route applies are questions for your export-compliance team and counsel. The rules explain why they will ask three things of every shot: what it contains, where and to whom it will be shown, and whether that information is already public somewhere they can point to.
The handoff is a release question too
The check does not start at posting. Under the ITAR, an export includes “releasing or otherwise transferring technical data to a foreign person in the United States (a deemed export)” (22 CFR 120.50), and technical data can be released through “visual or other inspection” (22 CFR 120.56). The EAR has a parallel deemed-export rule for technology (15 CFR 734.13). So before CAD leaves your company, your export-compliance team decides whether those files may go to an outside studio at all, which people there may see them, where they may be stored, and whether rendering may happen on machines outside the United States.
The simplest path is often to hand over less. A model built from a simplified outline drawing or released marketing geometry, rather than engineering CAD, removes most of these questions before they arise. The animation can still be accurate about what it shows. Client files also stay out of any AI tool whose terms allow training on them unless the client agrees in writing, as Blendpipe’s AI practices set out.
Contract clauses
Defense contracts can add a separate approval. DFARS 252.204-7000, “Disclosure of Information”, says the contractor “shall not release to anyone outside the Contractor’s organization any unclassified information, regardless of medium (e.g., film, tape, document), pertaining to any part of this contract or any program related to this contract” without the contracting officer’s prior written approval, unless the information is already in the public domain or another listed exception applies. Requests go to the contracting officer “at least 10 business days before the proposed date for release”, and subcontractors submit them through the prime contractor (DFARS 252.204-7000). Whether the clause is in your contract, and whether a given film falls under it, is your contracts team’s call. If it does, the 10 business days belong in the schedule before the trade show, not after it.
If it is unclear whether a product falls under the ITAR at all, the State Department’s Directorate of Defense Trade Controls determines that through a commodity jurisdiction request (22 CFR 120.12). That question is usually settled long before a launch film, but its answer decides which of the rules above your reviewers apply.
Example (fictional). Kelvane is an invented maker of a rugged satellite terminal, not a client, and every figure here is an illustration. It wants a 45-second launch film with 30 seconds of 3D for a trade show in the United States. Its STEP export has 412 parts. The visibility list keeps 57 visible parts, replaces 188 fasteners with 6 instanced fastener models, and hides the other 167 internal parts; 57 + 188 + 167 = 412. Kelvane’s export-compliance reviewer (in this example) asks for the radio module to appear as a plain block, so the cutaway shows the layout described on the public datasheet and nothing finer. The 3D runs 30 seconds at 24 fps, or 720 frames. At 8 minutes per frame on one machine that is 720 x 8 = 5,760 machine minutes, or 96 machine hours per pass; on 5 machines, 96 / 5 = 19.2 clock hours per pass, and three passes take 57.6 clock hours. Because Kelvane’s contracts team decides the disclosure clause in one of its contracts applies, the plan dates the request to the contracting officer 15 business days before the show, 5 more than the clause’s minimum.
Delivery formats that keep the asset reusable
Ask for the model in a form you can open again without the studio that built it: the render scene, a render mesh at a named tolerance, a glTF file for real-time use and a USD package if your partners work in USD, each traceable to the CAD revision it came from. A model that exists only inside one studio’s project files is a model you pay to rebuild.
The general case for reusing one product model across stills, product pages and AR viewers is set out in CGI versus product filming. A model built from CAD adds three requirements of its own:
- Traceability. The CAD revision is in every file name and in the readme, so when engineering issues a new revision you can tell which parts of the model are out of date.
- Tolerance. Each part’s tessellation tier is recorded, so a future close-up knows whether the mesh will hold or the part must be tessellated again from the STEP file.
- Units and axis. Written into the file, not assumed. glTF is in meters by definition; in USD, metersPerUnit and the up axis should be authored rather than left to the fallback.
glTF for real-time use
The Khronos Group describes glTF as “a royalty-free specification for the efficient transmission and loading of 3D scenes and models by engines and applications”, and glTF 2.0 was published as the international standard ISO/IEC 12113:2022 (Khronos, glTF). Because glTF stores triangles, the glTF file is always a tessellated and usually decimated copy of the model, never the master. Khronos publishes a glTF Validator that checks assets against the specification, which makes a quick acceptance test at handover.
OpenUSD for scene assembly
OpenUSD, originally developed at Pixar, describes itself as “a high-performance extensible software platform for collaboratively constructing animated 3D scenes”, with composition that combines assets “into larger assemblies” (OpenUSD documentation). Its geometric prims include NURBS surfaces as well as meshes. For a product family where the same parts recur across many scenes and films, a USD package can keep one source of truth for each part.
| Deliverable | Best for | What to check at handover |
|---|---|---|
| Render scene (the studio’s software) | Future films and new shots from the same setup | Software version, plug-ins, linked textures packaged |
| Render mesh at a named tolerance | Re-lighting, new cameras, other studios | Tolerance and CAD revision in the file name |
| glTF or GLB (decimated) | Web viewers and other real-time uses | Passes the glTF Validator; scale in meters; colorways as variants |
| USD package | Pipelines and partners that assemble scenes in USD | metersPerUnit and up axis authored, not left to defaults |
| Textures and material sheet | Any rebuild | Every finish callout mapped to a material name |
| Readme | Everyone who opens the files later | CAD revision, units, up axis, tolerance, reviewers who signed |
Who owns a model built from your CAD, and whether the studio delivers its working files, is set in the contract. Licensed 3D assets used around the product, such as stock environments, textures and HDR lighting images, carry their own terms, which belong on the rights sheet (see rights and usage and deliverables).
Reviews, sign-offs and the render plan
Each review checks one thing, and each has one named owner. Engineering checks accuracy, the product or brand owner checks the look, and export compliance and communications check release. Mixing them into one end-of-project review is how a finished, lit, rendered shot gets sent back for a hinge axis.
| Gate | What is reviewed | Who signs | What a change costs after it |
|---|---|---|---|
| Input register | Files, revisions, visibility list, release status of the inputs | Engineering and export compliance | Rebuilding the affected parts |
| Dimension check | Three measured dimensions against the drawing | Engineering | Rescaling, re-lighting |
| Greycard | Cameras, timing, explode order, motion limits, untextured | Engineering and marketing | Re-animation of the shot |
| Look development | Materials against the physical sample | Product or brand owner | New material passes |
| First render pass | The full shot, lit and composited | All reviewers | A full re-render of the shot |
| Final and versions | Every length, ratio and still pulled from the film | Release reviewers again | Re-export of every version |
The greycard deserves its place. It is the stage where the shot is real enough for an engineer to judge motion and too rough for anyone to mistake for the final. The broader sequence of boards, animatic and previs is covered in storyboards, animatics and previs.
The last gate repeats the release check on purpose. A cutdown, a vertical crop or a still pulled for a press kit can show a frame on its own, without the context the full film gave it. Each version and still is a separate item in the release record.
Planning render time
Rendering is machine time, and it belongs in the schedule as firmly as a review. The render time calculator does the arithmetic; with the fictional Orlenna numbers it runs like this. Eleven seconds of 3D at 24 fps is 11 x 24 = 264 frames. At 6 minutes per frame on one machine, one pass is 264 x 6 = 1,584 machine minutes, or 26.4 machine hours. On 4 machines that is 26.4 / 4 = 6.6 clock hours per pass, and three passes take 6.6 x 3 = 19.8 clock hours.
Those numbers assume frames split evenly and none fail. Two CAD-specific risks push them up. A late engineering revision after the greycard means re-tessellating the changed parts and re-rendering every shot they appear in. And a finer tolerance on hero parts raises the time per frame, so the test frame used for planning should come from the heaviest close-up, at its final tolerance.
Checklist: what to send with your CAD
Send the package below with the brief, and the plan can be built around real files instead of assumptions.
Files
- STEP AP242 export of the full assembly, with the revision letter in the file name
- One small sample export sent first, to check names, hierarchy and colors survive
- Native files only if the studio runs the same CAD and your policy allows it
- The released drawing with three dimensions marked for the dimension check
Show, simplify or hide
- The parts list marked part by part: show, simplify or hide
- Internal parts in any cutaway or exploded view decided individually
- Labels, plates and markings as current artwork, with placeholders for unit-specific data
Look
- Finish callouts for every visible part: color reference, gloss, texture, coating, transparency
- A physical sample, or photos of one beside a gray card under neutral light
- Every colorway the product ships in
Motion
- Hinge axes, travel limits and the order parts come apart
- Any speed or timing that will be shown on screen
Release and reviewers
- Your export-compliance team’s instructions for the files and the frames, including who may see the files and where they may be stored and rendered
- Any contract clause that requires approval before release, and its lead time
- Named reviewers for accuracy, look and release, with the days each review needs
Handover
- The deliverables you want back: render scene, render mesh, glTF, USD, textures, readme
- Ownership of the model and working files, settled in the contract
If you are planning the launch film itself, the 3D and CGI service page describes how a model built from CAD is reviewed as a greycard and rendered, and the aerospace and defense and technology and SaaS pages show how the review steps sit in a schedule. Whether a shot should be rendered or filmed at all is a separate decision, covered in CGI versus product filming. When the files and reviewers are ready, send a brief with the handoff package, the placements and the date the film must be shown.
