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, a floor-to-floor, anything. It lets the studio verify the import landed correctly instead of discovering the error at draft stage.
Fix those five and most import problems disappear entirely.
How do you specify camera angles without ambiguity?
Camera count is your scope, your price, and your deadline. Vague camera instructions are the most expensive vagueness in the whole brief.
“A nice view of the front” is not a camera. It is a hope.
Four ways to specify a view properly, in descending order of reliability:
- Save named views in your 3D model and list the names. Nothing beats this. The studio matches your camera exactly.
- Mark arrows on a PDF floor plan or site plan showing position and direction. Fast, unambiguous, works with any software.
- Send a screenshot from your own model viewport. The studio can match the angle by eye within minutes.
- Describe it in words, with a reference image. Least reliable, but workable if you also state eye height and roughly what should be in frame.
Also state whether each view is eye level, elevated, or aerial. A camera at 1.6 metres and a camera at 30 metres are different images of the same building, and only one of them is what you pictured.
What do you need to say about materials and finishes?
Name the actual product wherever you can. “Grey stone” covers several hundred materials that photograph nothing alike, and the studio will pick one of them.
For each significant surface, give the studio one of these: a supplier product name and code, a link to the product page, a photograph of a physical sample, or a reference image showing the finish in use. Any one is enough. None is a guessing game.
The left column is what studios usually receive. The right column is what removes an entire revision round. The difference costs you about two minutes per surface.
| Surface | Weak instruction | Instruction that works |
| Facade cladding | Light stone | Porcelain panel, sand beige, honed, 600×1200, supplier link |
| Window frames | Dark frames | RAL 7016 anthracite, matt powder coat |
| Flooring | Wood floor | European oak, 190mm plank, natural oil, product photo attached |
| Roof | Metal roof | Standing seam zinc, pre-weathered grey, 430mm bays |
| Landscaping | Some planting | Mediterranean species, olive and lavender, mature at handover |
What should the brief say about deliverables?
Six lines, and this section is what your invoice is actually based on.
- Number of images. Count them. This is the scope.
- Resolution and aspect ratio. Print needs more than web. State the intended use and let the studio advise.
- File format. JPG or PNG for most uses, TIFF for print, and ask for layered files if your team does its own post-production.
- Time of day. Day, dusk, or night. Dusk renders read as more expensive and are the default for launch campaigns, but say so rather than assuming.
- Branding and overlays. State whether the studio should leave clean plates for your designers to add text.
- Deadline, and what it is tied to. A tender date behaves differently from a nice-to-have. Studios sequence work around real deadlines when they know which is which.
| See how a white-label studio scopes a full render package from a single brief. Read the white-label guide |
The complete 3D rendering brief template
Copy this into an email or a document, fill it in, and send it with your files. It takes about ten minutes and it covers everything above.
Want the fillable version instead? Enter your name and email below and we will send the complete checklist straight to your inbox, ready to fill in and send with your files.
If you fill in nothing else, fill in the views, the materials, and the deadline. Those three carry most of the risk. View count is also what sets your price, so it is worth reading alongside our architectural rendering cost breakdown and the realistic timelines by project type.
What are the most common briefing mistakes?
Four keep appearing, across firms of every size.
The first is sending the model without the drawings. The studio then has no way to sanity-check dimensions, so import errors survive until you spot them in a draft.
The second is describing mood but not specification. Pages of adjectives about atmosphere, nothing about what the facade is made of. Atmosphere is the easy part.
The third is a camera list that grows after production starts. Adding a view is new work, not a revision, and it needs re-quoting rather than absorbing.
The fourth is silence about the deadline’s real nature. A studio that knows your date is a tender submission will sequence differently from one that assumes it is flexible. Tell them, and if you are still shortlisting, ask them the ten questions that separate studios.
What are the challenges and limitations?
A template cannot save a project where the design is still moving. If the facade is unresolved, no brief will stop the render changing, and pretending otherwise just moves the argument later. In that situation the honest move is to render the parts that are settled and stage the rest.
Over-specification carries its own cost. A brief that dictates every leaf and every reflection removes the studio’s judgement, and studios earn their fee partly on composition and lighting decisions you did not think to ask for. Specify what matters commercially and leave the craft alone.
Some projects genuinely cannot brief in advance. Competition work often starts before the design is fixed. That is fine, but it should be priced as exploratory rather than production, and both sides should say so out loud.
The template is a floor, not a ceiling.
How Archvizly handles briefs
Archvizly works as a white-label production partner for architects and design firms, real estate developers, interior designers, construction firms, hospitality brands and property marketing agencies. Brief intake happens before anything is quoted, not after, because a quote built on an incomplete brief is a quote that changes later.
We review the files first and tell you what is missing while it is still cheap to fix. If the model is in the wrong units, sitting three kilometres from the origin, or missing its texture folder, you hear about it on day one rather than at first draft.
Everything inside the agreed brief is flat-priced, including revisions, which is the other half of why the brief matters so much. You can read how that works in our guide to rendering revisions and what counts as new scope.
| Send your files and get a scoped quote, not a guess. Book a scoping call |
Frequently asked questions
What is a 3D rendering brief?
A 3D rendering brief is a short written document that tells a visualization studio what to build, what views to produce, what the surfaces are made of, and what files to deliver. It typically includes the 3D model, 2D drawings, a material schedule, reference images, a camera list, and a deadline.
What files do I need to send a rendering studio?
At minimum a 3D model or CAD geometry. Ideally also 2D plans and elevations, a material and finish schedule, reference images for mood, and a marked-up plan showing camera positions. Native files from your own software are always better than converted exports.
What file format is best for architectural rendering?
Native formats first: RVT for Revit, SKP for SketchUp, PLN for ArchiCAD, 3DM for Rhino. If native is not possible, FBX carries geometry and some materials well, and IFC is the most reliable neutral format for geometry and building data. IFC is standardised as ISO 16739 by buildingSMART.
Can a studio work from just a floor plan?
Yes, but it becomes a modelling project rather than a rendering project, and it costs more and takes longer. Say up front that no 3D model exists so the studio prices modelling time instead of assuming a finished model is on the way.
Why does my model open at the wrong size?
Almost always a units mismatch. A model built in millimetres interpreted as metres arrives a thousand times too large. Confirm and state your model units in the brief, and include one known dimension such as a door height so the studio can verify the import.
What does purging a model actually do?
Purging removes unused families, materials, views and objects that are still stored in the file. It routinely halves file size, speeds up transfer, and reduces import errors. In Revit it is Manage then Purge Unused. Most BIM and CAD tools have an equivalent.
How do I show the studio which camera angles I want?
The most reliable method is saving named views inside your 3D model and listing the names in the brief. Next best is arrows marked on a PDF plan showing position and direction, then screenshots from your own viewport. Describing views in words alone causes the most revisions.
How specific do materials need to be?
Specific enough to remove the guess. A product name and code, a supplier link, a photo of a sample, or a reference image showing the finish in use are all sufficient. “Grey stone” is not, because it covers hundreds of materials that photograph nothing alike.
Should I include my budget in the brief?
Yes. A budget range lets the studio propose a scope that fits rather than quoting something you will not proceed with. Withholding it usually produces a quote for the wrong project and adds a round of back and forth.
Does a better brief actually reduce cost?
It reduces revision rounds, which is where unplanned cost accumulates. Published 2026 studio pricing puts extra revision rounds at roughly 100 to 400 USD each, and most exhausted revision allowances trace back to something the brief never specified.
What if the design is still changing?
Say so in the brief and treat the work as exploratory rather than production. Render what is settled, stage the rest, and agree that design changes will be re-quoted as new work rather than absorbed as revisions.
Do I need an NDA before sending files?
If the project is unreleased, confidential, or tied to a competitive tender, yes. A studio doing white-label or overflow work should offer an NDA as standard rather than waiting to be asked.
