The direct answer
What to do first
Check the model's visual fit, then confirm the practical details that affect your scene: file format, software and version, linked textures, scene units, and permitted use. Use the detail page for the information it shows, and mark anything missing as a question to resolve before you start work.
1. Start with the five-minute fit check
Look at the model in the context of your brief. Does the silhouette, apparent scale, color direction, and visible material fit the room? Open the detail page and make sure the title, category, Space, and available description match what you think you are choosing.
If you are comparing several options, save them to a private project board and use a note or rating to record the decision. This keeps visual preference separate from the technical checks below.
2. Check the file format and software version
Confirm the file format your application can open and the software or renderer version the asset expects. If the listing does not show one of these fields, look for it in the package information or the source terms before starting a scene.
A model can look right and still need a conversion step. Plan that step before a deadline, especially when the asset comes with a scene file, linked materials, or renderer-specific settings.
- Format: can your application open the delivered file or archive?
- Version: does the model target your software and renderer version?
- Conversion: do you have a safe place to test an import before production?
3. Check textures and dependencies
Look for the texture files and external dependencies your scene needs. Check whether maps are included, whether their paths can be relinked, and whether the materials still look right after a test import. A preview can suggest a material direction, but only the package tells you what you have to relink or rebuild.
Keep a small test scene ready for unfamiliar assets. It is faster to discover a missing texture or plugin requirement there than after the model has been placed throughout a client scene.
4. Check scene units and scale
Confirm the scene units and the object's expected scale before you position it. Compare a known reference such as a door, chair seat, counter, or room dimension. Correct scale early prevents camera, lighting, and layout surprises later.
If the units are missing, import the model into a test scene and measure a visible reference before committing it to the project.
5. Check permitted use
Confirm that the terms allow your intended use, such as a client presentation, commercial rendering, team handoff, or any redistribution required by the brief. Keep that answer with the project record so the final handoff is easy to explain.
If the terms are unclear, pause the asset and choose a candidate whose use is clear enough for the project.
6. Check access and plan the download
An account is required for authenticated saving and download access. Free accounts receive 20 new asset acquisitions per UTC calendar month, so check the final shortlist before using a new acquisition. A re-download of an asset already acquired by the account does not use another unit.
Once the format, version, textures, units, and permitted use are clear, download the candidate and run the test import before building the full scene.
Keep this beside the project
A short checklist
- The model fits the room brief and its visible identity is clear.
- File format and the target software/renderer version are compatible.
- Textures, map paths, and external dependencies are accounted for.
- Scene units and scale were checked against a known reference.
- Permitted use matches the project and handoff.
- A test import succeeds before the model enters the full scene.
Read the documentation