What to Send Your Rendering Studio: The Complete 3D Rendering Brief Checklist
A studio once sent us a 340 MB Revit file, a photo of a hand sketch, and the words “make it look nice, need it Friday.” We shipped on Friday. The first draft was wrong in four separate ways, and every one of them traced back to something nobody had written down. The model was fine. The brief was the problem. A 3D rendering brief is a short written document that tells a visualization studio what to build, what to show, and what to deliver, covering the source files, the camera list, the materials, and the output specification. It is not a design description, which explains your intent, but a production specification, which removes the studio’s need to guess. The distinction matters because guesses are expensive. Every unstated assumption becomes a revision round, and revision rounds land on your deadline rather than the studio’s. A good brief is not paperwork. It is the cheapest insurance available on a rendering project. Ten minutes of writing saves three days of correcting. What is a 3D rendering brief? A brief answers five questions before anyone opens a 3D application: what is the building, what views do you want, what do the surfaces look like, what files do you need back, and when. That is the whole job. Everything else is detail hanging off those five. Studios that ask for a brief are not being bureaucratic. They are trying to price the work accurately and avoid the conversation where you say “that is not what I meant” three days before a tender goes out. A studio that does not ask for one is either very experienced with your practice or about to guess. The American Institute of Architects makes the same argument about owner-architect agreements: scope of services and deliverables have to be written down, or the dispute simply arrives later at a worse moment. A rendering brief is that principle applied to a much smaller contract. What files does a rendering studio actually need? Six things, and only the first is genuinely mandatory. The rest reduce the number of decisions the studio has to make on your behalf. Read the right-hand column first. If you can send the native file from your own software, send it. Converted files lose information every time they change hands, and the studio then spends billable time rebuilding what the export dropped. What to send Why the studio needs it Acceptable formats 3D model or CAD geometry The base for everything. Without it there is no project RVT, SKP, PLN, 3DM, DWG, FBX, IFC, OBJ, MAX 2D drawings: plans, elevations, sections Confirms dimensions and catches model errors PDF, DWG, DXF Material and finish schedule Stops the studio inventing your specification PDF, XLSX, supplier links, photos Reference images Communicates mood and lighting faster than words JPG, PNG, Pinterest board, PDF Camera list or marked-up plan Defines the deliverable count. This is the scope PDF markup, sketch, screenshot, view names Site context, if the setting matters Determines what appears around the building Photos, survey, DWG site plan, map link If you only have a sketch and a floor plan, say so. A studio can work from very little, but it needs to know that up front so it prices modelling time rather than assuming a finished model is coming. Which format should you export from your software? This is the table most briefing guides skip, and it is the one that saves the most time. Native beats converted in almost every case, because conversion is where geometry, materials and units quietly go wrong. Your software Send this What survives What usually breaks Revit RVT native, or FBX from a 3D view Geometry, levels, family names Materials often need rebuilding SketchUp SKP native Geometry, groups, components, textures Very little. Best case for archviz ArchiCAD PLN native, or IFC Geometry, storeys, element data Surface finishes and textures Rhino 3DM native Precise NURBS geometry, layers Materials. Rhino materials rarely transfer AutoCAD DWG, plus PDF of sheets 2D linework, dimensions, layers No 3D unless the model is 3D solids 3ds Max MAX native, plus texture folder Everything, if textures are included Missing texture paths on the studio’s machine Vectorworks VWX, or IFC and DWG Geometry and layer structure Renderworks materials Any BIM tool IFC as the fallback Geometry and object data reliably Appearance. IFC carries data, not looks On that last row: IFC is published by buildingSMART and standardised as ISO 16739, which makes it the most dependable neutral format for geometry and building data. It is not a good carrier of visual appearance, so treat an IFC as a reliable shell that still needs its materials specified separately in the brief. For Revit specifically, Autodesk documents both routes: exporting a 3D view to DWG with ACIS solids and exporting to FBX for 3ds Max. FBX from an open 3D view is usually the better handoff for rendering work. Not sure what your file will lose in translation? Send it and we will tell you before quoting. Talk to Archvizly What breaks a model before it reaches the studio? Five things, and all five are fixable in under ten minutes by the person who built the model. None are fixable quickly by the person receiving it. Wrong or mixed units. A model built in millimetres opening as metres arrives a thousand times too big. Set and confirm units before export. This is the single most common handoff failure. Geometry far from the origin. Models georeferenced to real-world coordinates can sit kilometres from 0,0,0, which causes visible flickering and precision errors in render engines. Move the model near the origin, or tell the studio the offset. Unpurged files. That 340 MB Revit file was mostly deleted families and unused views. Purge unused before exporting. Files routinely drop by half. Missing textures. Custom materials reference image files on your machine. Send the texture folder alongside the model, or the studio opens a grey building. No indication of scale. Include one known dimension, a door height,



