Most “3D NFTs” fail for a boring reason: the file is a mesh with a JPEG stuck on it, not a PBR material a viewer can light. Web3 marketplaces and in-browser viewers are just glTF (or similar) players with a default HDRI. If you author metalness/roughness maps correctly, the collectible looks like an object. If you do not, it looks like a screenshot of an object. This article stays practical: formats, licenses, and file size—not token prices.
Why PBR matters for 3D collectibles
A token can point at a GLB, a marketplace iframe, or a custom viewer. The buyer will rotate the asset under lighting you do not control. PBR is the contract that says “this gold is metal, this leather is rough” regardless of the environment. That is the same reason games and archviz adopted PBR. Use albedo without baked shadows, a real roughness map, a metallic map that is 0 or 1 except on mixed surfaces, and a tangent normal. Fundamentals: what are PBR textures and albedo, normal, and roughness.
glTF is the portable package
Export glTF 2.0 / GLB with the metallic-roughness model. It is what OpenSea-style 3D previews, Sketchfab embeds, and most WebXR viewers expect. Optional extensions (clearcoat, transmission, sheen) look great in a full Khronos viewer and often disappear in a mobile marketplace. Design the hero look with the core four maps first. Validate with the Khronos glTF Validator and Sample Viewer. Keep transforms applied, scale in meters, and a single default material per object unless you truly need more. If you also keep a Blender source file, you can re-export when a platform changes its viewer.
License traps: CC0 is not “your” NFT
Locker3d textures are free under a CC0-style grant: use them, modify them, ship them commercially, no attribution required. That does not mean you can mint the texture files as exclusive original art. The maps are public domain; anyone else can use the same oak floor. Your NFT, if you issue one, should be the model, the composition, the animation, or the experience you actually made. Do not scrape a CC0 pack, flip it, and call it a limited drop. Read CC0 textures: what you can and cannot do and PBR texture licenses explained before you write a token description.
File size and map discipline
Viewers on phones will not stream eight 8K EXRs. Use 1K or 2K, JPEG or WebP for albedo if the platform allows, and PNG for data maps when you need clean roughness. Pack occlusion/roughness/metallic when the exporter supports it. Instance repeated materials instead of unique maps on every bolt. Tileable CC0 surfaces from the Locker3d catalog—metal, leather, marble—keep files small and legal. Compression notes: texture compression for realtime.
A short checklist before you list an asset
1) Core PBR maps, correct color space. 2) GLB opens in the Khronos viewer and looks like your Blender lookdev, not a plastic toy. 3) License text states what you created vs what is CC0. 4) File size fits the marketplace cap. 5) You are not selling someone else’s scan as exclusive. If you need more materials, browse free PBR textures and keep a local library. More production notes: blog and software.
Frequently asked questions
Can I mint a 3D NFT that uses Locker3d textures?
You can include CC0 maps in a model you mint, because CC0 allows commercial use and redistribution. You cannot claim the textures themselves are your original art or an exclusive NFT. The token should represent your model, scene, or compilation—not the public-domain maps.
What file format should a 3D NFT use?
glTF or GLB with metallic-roughness PBR is the format most marketplaces and viewers understand. Keep albedo, roughness, metallic, and normal. Test in the Khronos glTF Sample Viewer before you upload.
Why does my NFT look flat in the marketplace preview?
Many previews use a basic glTF shader, a small environment, and heavy compression. If albedo has baked lighting or roughness is in the wrong color space, the viewer has nothing to work with. Fix the maps; do not only raise contrast in a screenshot.