Why Browser Optimization is Not Optional
To fully leverage the incredible communicative power of Lobbi's in-browser native 3D model viewer, your artistic assets need to be exported cleanly and efficiently. The goal of uploading a WIP asset to Lobbi isn't to run a 4K physics simulation; it is purely to communicate visual intent and topological structure to an Art Director swiftly.
If you upload a bloated, unoptimized 2GB raw sculpt, you entirely defeat the purpose of the platform by forcing the reviewer to wait fifteen minutes simply for the webpage to buffer the geometry. Speed is paramount. An optimized pipeline is a fast pipeline.
Configuring Global Export Settings
Whether you are commanding Autodesk Maya, executing in Blender, or iterating in 3ds Max, fundamental export laws apply. Crucially, ensure your global scale is explicitly set linearly before confirming export (e.g., locking 1 unit = 1 meter is the unquestioned industry standard).
You must absolutely "Apply All Transforms" (specifically scale and rotation matrices) natively within your software package before generating the file. A model exported with unapplied scale data will often drastically inflate or warp improperly when rendered via our WebGL viewer. While our robust viewer technically supports FBX, OBJ, and raw GLTF formats, we highly strongly recommend compiling your assets into binary GLB files for the absolute fastest, most reliable web parsing.
The Art of Embedding Textures Successfully
A painfully common, momentum-killing mistake made by junior artists is uploading a bare, geometry-only OBJ file without its accompanying MTL file or explicitly linked albedo/specular map textures. This always results in a devastatingly flat, solid gray untextured model appearing in the shocked viewer.
Always export your final review assets explicitly as binary FBX files with the critical "Embed Media" checkbox ticked within your specific exporter UI, or even better, aggressively pack all your PBR textures directly into a unified, single GLB file. This strictly guarantees that when the frantic Art Director inevitably opens that character model on their iPhone while riding the subway, they actually see the fully mapped PBR sub-surface scattering, not a broken, colorless wireframe.
Strict Polycount Budgets for Web GL
While the modern internal architecture of Unreal Engine 5 via Nanite can lazily handle chaotic millions of unoptimized polygons with ease, our specific browser viewer is hyper-optimized for instantaneous speed across a wide spectrum of mobile and desktop hardware.
If you are stubbornly attempting to upload a raw ZBrush master sculpt severely exceeding 5 million polygons purely for visual anatomical review, immediately reconsider. Instead, upload a quickly decimated version or a low-poly bake to the Lobbi portal purely for visual sign-off, explicitly linking the heavy high-res raw file via a cloud link deep in the asset description. This ensures the review sheet loads instantly for critical leads stuck on weak mobile connections.
Troubleshooting Inverted Normals
The most common visual bug reported to our pipeline support team is a model rendering entirely inside-out or appearing dramatically transparent from certain viewing angles. This is uniformly caused by inverted face normals during the geometry export phase, not a bug in the Lobbi viewer.
Before exporting from Blender, consistently use the "Recalculate Outside" command to explicitly unify the normal directions of all faces. Similarly, in Maya, utilize the "Set to Face" command to ensure the directional lighting will bounce correctly within the WebGL environment.
Experience the 3D Viewer
Stop waiting for heavy engine builds to compile just to verify UVs.
Leverage our hyper-fast, universally compatible 3D model viewer perfectly integrated directly into your team's workflow workspace today.