You’ve spent hours modelling. You hit render. And something feels… off. Shading looks plastic, textures stretch across the surface, the lighting bounces oddly, and the whole scene screams “CGI” instead of “photograph”. The problem is almost never the render engine. It’s what happened (or didn’t happen) before you pressed that button.
At Points Brighton, we’ve delivered hundreds of visualisation projects, and the pattern is consistent: photorealism is won or lost in the preparation stage. This guide walks you through the exact pre-render workflow we use in 2026, structured as a checklist so nothing gets missed.
Why Preparation Matters More Than the Render Engine
Cycles, V-Ray, Corona, Redshift, Octane. It doesn’t matter which engine you use. If your model has flipped normals, non-uniform scale, overlapping UVs, or a missing displacement map, the output will look wrong regardless of how many render samples you throw at it.
Think of render prep like prepping a car before a paint job. Skip the sanding, and no amount of expensive paint will hide the flaws.
The Pre-Render Checklist at a Glance
| Stage | Goal | Common Mistake to Avoid |
|---|---|---|
| Topology cleanup | Clean mesh flow, no n-gons in visible areas | Leaving unmerged vertices and flipped normals |
| Scale correction | Real-world units, transforms applied | Non-uniform scale breaking shaders |
| UV unwrapping | Even texel density, no overlaps | Stretched or seam-visible UVs |
| Material assignment | PBR-accurate values, correct texture slots | Using sRGB textures in linear channels |
| Final sanity check | Scene ready, no hidden issues | Rendering without a test frame |
Step 1: Clean Up Your Topology
Bad topology creates shading artefacts that no render engine can hide. Before anything else, run through this cleanup pass.
Topology Checklist
- Merge duplicate vertices (in Blender: Mesh > Merge > By Distance).
- Recalculate normals outside and check for any dark or flickering faces.
- Remove n-gons on curved surfaces where subdivision or smoothing will be applied.
- Delete interior geometry that will never be seen by the camera. It just slows the render.
- Add supporting edge loops around hard edges so bevels catch light correctly.
- Use weighted normals or bevel modifiers on mechanical objects to get crisp highlight reflections.
A pro tip: enable matcap or clay shading and orbit your model. Any shading glitches will scream at you before you ever hit render.
Step 2: Fix Scale and Transforms
This is the single most overlooked step, and it silently ruins physically-based renders.
Physically-based render engines calculate light falloff, subsurface scattering, depth of field, and even bevel widths using real-world units. A sofa that is 200 metres wide in your scene will scatter light like a building, not furniture.
- Set your scene units to metric (metres or centimetres depending on scale).
- Measure your object against a reference. A door should be around 2.0m tall, a coffee mug around 9cm.
- Apply all transforms. In Blender: Ctrl+A > All Transforms. In Maya: Freeze Transformations. In 3ds Max: ResetXForm.
- Ensure scale values read 1,1,1 and rotation reads 0,0,0 on every object before export or shading.
Non-uniform scale is particularly nasty. It stretches procedural textures, distorts bevels, and makes any modifier that depends on distance behave unpredictably.
Step 3: UV Unwrapping Done Right
UVs are how your 2D textures wrap onto your 3D surface. Bad UVs produce visible seams, blurry patches, and stretched patterns that instantly break realism.
UV Checklist
- Mark seams in hidden areas (under the object, behind edges, along natural creases).
- Maintain consistent texel density across all objects in the scene. A brick wall and a doorknob should have proportional pixel-per-metre resolution.
- Avoid UV overlaps unless you are intentionally mirroring for tileables.
- Use a UV checker texture (a grid of coloured squares) to verify no stretching or squashing.
- For hero objects (foreground close-ups), give them their own UV set with more space in the 0-1 UV square.
- Pack UVs efficiently, but leave a small padding to prevent bleeding at mipmap levels.
When You Can Skip UV Unwrapping
Purely procedural materials (using noise, voronoi, or triplanar projection) don’t need UVs. But the moment you introduce a bitmap texture, decal, or baked map, proper UVs become mandatory.
Step 4: Assign Materials with PBR Discipline
Physically-based rendering (PBR) is the standard because it produces predictable, realistic results. But only if you feed it correct values.
PBR Material Rules
| Texture Type | Colour Space | Notes |
|---|---|---|
| Base Colour / Albedo | sRGB | No baked-in shadows or highlights |
| Roughness | Non-Color / Linear | Black = mirror, White = matte |
| Metallic | Non-Color / Linear | Use pure 0 or pure 1 whenever possible |
| Normal Map | Non-Color / Linear | Check OpenGL vs DirectX orientation |
| Displacement / Height | Non-Color / Linear | Use for close-up detail only |
Material Sanity Checks
- Base colour values should never be pure black or pure white. Real-world dielectrics sit between RGB 30-240.
- Nothing is perfectly smooth. Even polished glass has microscopic roughness. Add a tiny roughness value (0.02-0.05) for realism.
- Vary roughness with a texture rather than a single value. Fingerprints, dust, wear patterns are what sell realism.
- Use IOR values correctly: glass 1.45, water 1.33, plastic 1.45-1.55, gemstones vary.
Step 5: The Final Pre-Render Sanity Check
Before you commit to a long final render, run this last verification pass.
- Do a low-sample test render at target resolution. Not a preview, an actual test at output size.
- Check for fireflies (bright white pixels), which indicate lighting or material issues.
- Verify camera focal length and aperture match a realistic real-world camera setup.
- Confirm HDRI or lighting intensity is producing correct exposure without needing extreme post-processing.
- Check all instances and linked data. It is common to update one object and forget its copies.
- Look at the render through a colour-managed view transform (AgX, Filmic, ACES). Never render or judge photorealism in raw linear view.
Common Mistakes That Kill Photorealism
After years of studio work, these are the culprits we see most often on client files sent to us for fixing:
- Objects with non-applied scale making bevels and displacement misbehave.
- All materials at 0.5 roughness, producing that classic “CGI plastic” look.
- Textures loaded in wrong colour space, especially roughness maps in sRGB.
- No secondary micro-detail on surfaces. Real objects have imperfections at every scale.
- Perfectly aligned, perfectly clean geometry. A slight rotation offset or edge wear does wonders.
- Using a single HDRI without any additional lighting, resulting in flat scenes.
Software-Specific Notes
Blender
Use the Principled BSDF for 99% of materials. Enable Cycles Experimental for adaptive subdivision on displacement. AgX is the recommended view transform as of 2026.
3ds Max with V-Ray or Corona
Use VRayMtl or CoronaPhysicalMtl. Always work in linear workflow with gamma 2.2 or ACEScg. ResetXForm on every imported object.
Maya with Arnold
aiStandardSurface is your default shader. Freeze transformations religiously. Use the Arnold denoiser only after ensuring your lighting is clean, not to hide noise from underlit scenes.
FAQ: Preparing 3D Models for Rendering
How long should render preparation take compared to modelling?
Expect prep to take roughly 20 to 30% of your modelling time for hero assets. Skipping this stage is the number one reason renders look amateur.
Do I need to retopologise a sculpted model before rendering?
For still renders where the model won’t deform, high-poly sculpts can be rendered directly. For animation, close-ups, or optimisation, retopology plus baked normal maps is the professional route.
What resolution should my textures be?
For hero objects seen in close-up: 4K (4096×4096). For mid-ground props: 2K. For background or small objects: 1K or 512px. Match texel density across the scene rather than blindly using 4K everywhere.
Is 32GB of RAM enough for 3D rendering in 2026?
For product visualisation and architectural stills, 32GB is comfortable. For complex environments with heavy geometry and 4K+ textures across many assets, 64GB is now the professional standard, and GPU VRAM (16GB minimum) matters just as much.
Should I model in triangles or quads?
Model in quads during creation for cleaner subdivision and edge flow. Triangulation happens automatically at render time and is not something you need to do manually unless exporting to game engines.
How do I know if my UVs are good enough?
Apply a UV checker texture. If the squares appear evenly sized and undistorted across your model, and seams fall in hidden areas, your UVs are ready for rendering.
Final Thoughts
Photorealism is not a button you press. It’s the sum of dozens of small correct decisions made before the render begins. Follow this checklist on every project and you’ll eliminate the most common failure points that separate amateur renders from professional visualisation work.
If you’d rather focus on your product, architecture, or creative vision and leave the technical rendering pipeline to specialists, the team at Points Brighton handles the full workflow, from raw CAD or model files through to final photoreal delivery. Get in touch through our contact page to discuss your project.
