Yes. All our assets are released under the CC0 license, meaning you can use them for absolutely any purpose, including commercial work. More about CC0 here.
Yes. The only thing you can't do is claim to be the original author or re-license them. More about the CC0 license here.
Please make it clear to your customers that these assets are free and public domain, and if possible include a link to Poly Haven.
If your product sells well, consider supporting the creation of these assets on Patreon.
Absolutely! We release all our assets under the CC0 license (essentially copyright-free in jurisdictions that support it) which allows you to do whatever you want with them, including training AI models. We would love to help the industry grow and we hope that providing a high quality dataset to train with can help improve the outputs of your AI models.
If you work for a company or research group that benefits from our library and would like to help us grow the dataset we make available for everyone, improving the quality of your own outputs, please help fund us.
Poly Haven does not itself do commissions, but our artists may be happy to work with you. Please get in touch and we can point you in the right direction.
Often we offer discounts if you allow us to publish your assets on Poly Haven too.
In short, donations from people like you, corporate sponsors, and advertising.
We publish the details of how we work financially in our public finance reports.
Generally speaking, an HDRI (High Dynamic Range Image) is simply an image that contains more than 8 bits of data per pixel per channel. Image formats like JPG and PNG are typically 8-bit and are sometimes referred to as 'LDR' (Low Dynamic Range) images, whereas image formats like EXR and HDR store more data and are therefore HDRIs.
However in the CG world (and on this site) we have come to use the term 'HDRI' to describe a 32-bit 360x180 degree equirectangular image that is used for lighting CG scenes.
HDRIs are often used as the only light source in order to create a very realistically lit scene or to match the lighting from video footage (using an HDRI shot on the same set as the video was taken). But of course, they are also used to complement standard lighting techniques and to add detail to reflections.
It's super easy, and no different from using any other HDRI. Here are some short videos to show you exactly how:
All our HDRIs are unclipped, meaning you'll get realistic results automatically and do not need to adjust the gamma or plug the image into the strength/intensity input.
The number of EVs (or 'stops') is based purely on the number of brackets captured. For example, 12 EVs means 5 photos were taken with 3 EVs between them (shutter speeds: 1/4000, 1/500, 1/60 1/8, 1"), and since there are 4 gaps of 3 EVs between them, the dynamic range is said to be 12 EVs (4x3=12).
Unfortunately, there is no standardized way for measuring the dynamic range of an HDRI. Different people use different methods, so there's no reliable way that you as a user can tell whether website-A which claims 50 EVs of dynamic range is actually better than website-B which claims 20 EVs.
The main thing to look out for is whether an HDRI is unclipped or not. They usually don't mention anything if it is indeed clipped, so watch out. Being unclipped means the full range of brightness in the scene was captured, including the super crazy bright sunshine. If an HDRI is clipped (AKA "clamped"), it will produce unrealistic lighting which is usually flat and lacking contrast.
This changes every now and then, and there are now multiple photographers shooting HDRIs for this site, so take a look at my article on creating your own HDRIs to answer your actual question ;)
These diffuse textures are actually albedo maps, designed for use in physically-based rendering engines. We use the term "diffuse" instead because it's a little more widely understood than "albedo", and a little more specific than "color".
For PBR rendering to look correct, albedo maps shouldn't contain any shading. Instead, shading is applied by the rendering engine itself, with the help of physical geometry displacement and path-traced shading, or a separate ambient occlusion map. Without real micro-displacement geometry, the separate ambient occlusion map can be used to simulate the effect that the real geometry would have on the shading in an average environment, typically only applied to indirect lighting.
This is why we remove as much shading from our diffuse maps as possible, though we can't always remove everything, and in some cases it's desirable to leave in microscopic shading which would not be reproduced by shading real geometry displacement anyway.
By contrast, diffuse maps used in older or non-photorealistic rendering engines are intended to contain shading. If you are working with such a rendering engine, or if you wish to reduce the distribution file size of your project, you can merge the albedo and AO maps together to create a traditional diffuse map. This can be done by multiplying the AO map over the albedo map in an image editor.
If you're using a download manager extension and are getting 404 errors on downloads, disable the extension for polyhaven.com.
If you use Firefox and have "Delete cookies and site data when Firefox is closed" turned on, then you cannot download our assets.
Solution: Disable this setting or use a different browser. More info here.
Why is this happening? When you download a model/texture on our site, your browser creates a "service worker" that pulls in all the separate required files like textures and meshes to create a zip file for you on the fly. This setting in Firefox prevents the service worker from being created, meaning downloads do not work.
We're not trying to be the next BlendSwap or Turbosquid, but we do accept donated assets that meet our strict quality standards.
Absolutely, but remember this is just one of the many tools available. Our goal is to create quality assets, and we'll use whatever methods are best for each case.
When we launched 3D Model Haven in 2020, we commissioned a few gun models from various authors to publish there. These have now been removed, as we assume their creators based their work on real-world gun designs, which is likely the intellectual property of the manufacturers.
This is a legal grey area we'd rather avoid - the models themselves are CC0, but the designs they may be based on probably aren't - so it's safer for everyone if we just remove them from the site.
In future, we plan to replace them with models based on original fictional designs.
Some of our assets make use of Blenders Geometry Nodes. More specifically the leaves on the trees are "instances/duplicates" of smaller leaf models and currently exporting the model without making the instanced geometry real results in the missing geometry not found in the FBX, GLTF, and USD formats.
We are working on fixing this issue, but in the meantime you can manually export the files by following the steps in this video.
Note* You will need Blender 3.0. or higher installed.