VR / AR 3D Models

Meta Quest 3 targets 72 fps on a Snapdragon XR2 Gen 2 GPU. A safe scene budget is 300,000–500,000 triangles total across all visible objects. Individual assets should stay under: characters 5,000–10,000 tris, hand-held props 500–2,000 tris, environment building modules 2,000–8,000 tris, and background decoration under 500 tris. Quest performance tanks quickly beyond 50 draw calls per frame, so batching and atlasing textures is more important than raw poly count. When buying, prioritise assets that explicitly list polygon counts in the description.

WebXR runs in the browser and uses GLB (binary GLTF 2.0) exclusively. GLB loads via Three.js GLTFLoader or Babylon.js SceneLoader, and the Khronos GLTF specification maps directly to WebGL / WebGPU calls. For WebXR, keep textures at 512×512 or 1024×1024 maximum and use KTX2 Basis Universal compression (GLTF KHR_texture_basisu extension) where possible — it reduces texture memory by 6–8× compared to uncompressed PNG. Total scene size should stay under 5 MB for fast wireless loading. Models from Proofly in GLB format are immediately usable in Three.js WebXR sessions.

Apple Vision Pro uses RealityKit and prefers USDZ format for AR Quick Look and visionOS apps. However, you can convert GLB and OBJ files to USDZ using Apple's Reality Converter (Mac app, free) or the command-line 'xcrun usdz_converter' tool. Reality Composer Pro (Xcode 15+) can also import FBX, OBJ, and GLTF/GLB and export to USDZ. For Unity PolySpatial (Unity XR for Vision Pro), standard GLB and FBX assets imported into Unity work directly. Most Proofly GLB and OBJ assets convert to USDZ without issue, though complex PBR shader setups may require manual material adjustment in Reality Composer.

VR assets render in a fully enclosed virtual environment — you control all lighting, so PBR materials work predictably. AR assets overlay onto the real world, so they need physically accurate materials that react to real-world lighting (important for ARKit/ARCore light estimation). AR assets typically need: lower polygon counts (mobile camera tracking is compute-intensive), real-world correct scale (1 unit = 1 metre), neutral base colours that read well under varying real-world lighting, and optional occlusion meshes for realistic depth sorting. Both VR and AR benefit from power-of-2 textures, minimal draw calls, and LOD variants.

VR assets need a second UV channel (UV2) if you plan to bake lightmaps — Unity's Progressive Lightmapper and Unreal's Lightmass require non-overlapping UV2 for static geometry. If your VR scene uses only real-time lighting (common in Quest apps to save GPU time), a single UV channel is fine. For AR, lightmaps are rarely used since lighting comes from the real world. When buying, check whether the listing mentions 'lightmap UVs' or 'UV2' in the description if you need baked lighting. Most game-ready GLB and FBX assets from Proofly include at least one clean UV channel.

Yes — most Proofly listings include a Commercial license that covers apps, games, and interactive experiences published for sale or download. Check the license badge on each model page: Personal, Commercial, or Extended. Commercial covers a single product/app. Extended covers templates or assets you redistribute to other developers. If you're building a VR training platform, multiplayer game, or enterprise AR tool that generates revenue, Commercial is the right license. For NDA projects or custom licensing terms, use the 'Message Creator' button to contact the creator directly.