Free 3D Models for Commercial Use: License and Selection Guide 2026

Free 3D Models for Commercial Use: License and Selection Guide 2026

A 3D model is not a picture of an object. It is the object, or close enough that a client, a game engine, or a 3D printer can rebuild it. Download a chair model and you may receive a mesh, a set of texture maps, a rig, and animation data in one folder. Each part travels into your deliverable in a different way, and the license has to cover the way you actually ship it: a rendered still, a real-time scene, an augmented reality viewer, a printed part, or, hardest of all, a file you hand over.

This guide covers free 3D models for commercial work. It compares sources whose license or support pages were read on their own sites for this guide, explains the Creative Commons variants you will meet on per-model downloads, and gives you a file routine and a checklist so the model you ship is one you can file and hand to a client without guessing.

This is practical guidance for working designers, not legal advice. For a paid campaign, a product sold at scale, or a model that becomes part of a brand mark, take the actual license texts to a qualified reviewer.

The Short Answer

For client work, start with a library that states one license for the whole collection, in one place you can save.

• Poly Haven - the license page states that all of its assets, including its 3D models, are licensed as CC0. In its own summary that means any purpose including commercial work, no credit required, and redistribution allowed, including inside a product you sell. The same page keeps the site itself separate: logos, example renders, and copy are not part of the CC0 grant, and scraping the site is restricted.
• ambientCG - the license page states that its assets are provided under the Creative Commons CC0 1.0 Universal License, covering the downloadable asset files and the material preview renders. It lists copying, modifying, distributing, and performing the assets, even for commercial purposes, and gives a video game as its example of including the raw files in a project. Credit is not required; a suggested credit format is provided.
• Kenney - the support page answers the commercial question directly for its game assets: they are public domain under CC0, usable in commercial projects, with the full terms in the license file included with each download. Credit is not required, and the page adds one limit that is easy to miss: do not use the Kenney logo, which is reserved for the studio's own projects.
• Quaternius - low-poly packs for games, listed on quaternius.com with formats and a license field on each pack page (the Ultimate Nature Pack page, for example, lists FBX, OBJ, and Blend formats). The license that ships inside the downloads is CC0 1.0. Save the license file from the pack you download; that file, not a search result, is your record.
• Smithsonian Open Access - the Open Access page invites visitors to download, share, and reuse the collection without asking, and describes more than 5.2 million 2D and 3D digital items across the Smithsonian museums, research centers, libraries, archives, and the National Zoo. Open Access items carry a CC0 designation, so check the item record for the model you take and save that record with the file.
• Sketchfab - two different systems sit under one name, and mixing them up is the most common error in this field. Downloadable models carry the license the uploader chose, shown on the model page. Store models are sold under the royalty-free license at sketchfab.com/licenses, which is a paid, single-seat grant with a standard and an editorial tier. Neither system works like a CC0 library, and both are covered in detail below.

The split matters more in 3D than in any other asset type on this site. A CC0 library grants the file itself. A per-model Creative Commons license grants the file under conditions you have to read model by model. A store license grants use inside your finished work and, as the Sketchfab terms put it in substance, forbids letting anyone else use or access the model as a stand-alone file.

For the audit across every asset type, pair this guide with the design asset licensing checklist, which runs the same questions over fonts, icons, photos, textures, and mockups in one pre-shipment pass.

Why 3D Models Break 2D Habits

Designers carry photo and illustration habits into 3D work and miss four differences that change both the license answer and the file answer.

1. A model download is a bundle, not a file. A typical download contains the mesh, texture images, a material setup, and sometimes a rig and animation clips. The texture maps inside the bundle are images in their own right; the textures and patterns guide covers how PBR map sets are licensed when they are sold as materials. When you take a model, confirm the license covers the whole bundle as delivered, including every part beyond the mesh you can see in the preview.

2. The deliverable often contains the model itself. A stock photo ships flattened into a layout. A 3D model ships as geometry inside a game build, a web viewer, an AR app, or a configurator, where a determined user can extract it. Licenses written for 3D know this. CC0 libraries answer it by allowing redistribution. Store licenses answer it by forbidding stand-alone access. Your delivery format decides which answer you need before you download anything.

3. Modification is normal, not optional. Rescaling, retopology, re-rigging, recoloring a material, cutting a model down for print, or merging two models into one scene are routine steps. A license with a NoDerivatives condition blocks sharing a modified version, which makes it a poor fit for production work even when the unmodified model may be shown. Read the modification line before you fall for the preview render.

4. A model can be a real product. Scanned museum objects, branded products, vehicles, furniture with a living designer, and architectural landmarks can all appear as models. A file license covers the digital file. It does not clear a trademark shown on the model, a design right in the object, or an endorsement your scene implies. The Smithsonian can dedicate its scan under CC0; that dedication does not make the depicted object's own history or marks yours to claim.

What a 3D Model License Actually Controls

Five questions decide whether a free model is safe for a given job. Read every source in this guide through these five, in this order.

1. Can the finished work be sold or used to promote a business? Commercial use covers a client product page, an ad render, a paid game, an e-commerce configurator, and a portfolio used to win work. The CC0 sources in this guide answer yes in plain terms. A Creative Commons license with an NC element answers no for commercial use. A store editorial license also answers no for commercial or promotional use.

2. Can the model file travel to the client, the buyer, or the player? This is the question 3D adds to every other asset type. Under CC0, the file can travel. Under the Sketchfab store license, it cannot be made available as a stand-alone file, sublicensed, or sold on. Under a per-model Creative Commons license, redistribution is allowed only on that license's conditions, including credit and, where SA applies, licensing the shared version under the same terms.

3. Is credit required, and in what form? CC0 sources here do not require credit. Creative Commons licenses built on BY require credit in the manner the licensor specifies: creator name, title, source link, and license name is the standard record. A credit that lives in a game credits screen, an app about page, or a product documentation file has to be planned before release, not added after a complaint.

4. Can you modify the model and share the result? CC0 allows modification without conditions. BY and BY-SA allow adaptations to be shared with credit, and SA requires the adaptation to be shared under the same license. ND blocks sharing adaptations. For a designer, ND is usually a stop sign: you cannot fix the mesh, adapt the rig, or kit-bash the model into a scene and then distribute that scene.

5. Does the model depict someone else's rights? A branded appliance, a current production car, a sports team's marks, or a private building can sit inside a perfectly licensed file. The file license and the depicted rights are separate. Use branded models descriptively, keep logos out of hero positions, and never let a render imply the brand hired you or endorses the product.

The Creative Commons Variants, Translated for Models

Per-model libraries label each download with one of the Creative Commons licenses. Creative Commons builds those licenses from four conditions, and the combinations decide what you can do. Read the label on the model page as four switches, not as a badge that says free.

Two habits keep this table useful. First, the version and the exact label on the model page are part of the record; a library search filter is a finding aid, not the license. Second, a model page can change its label or disappear. Save the model page, the label, and the download date in the project folder at download time.

Verified Sources Compared

The table below is the original comparison for this guide. Each entry was checked against the source's own license, support, or collection page for this guide. Read it as a map, then open the same page for the exact model you download.

How to read this table without fooling yourself. First, CC0 is a different category from a generous model page. Poly Haven, ambientCG, Kenney, and Quaternius let the geometry travel with your project. A store license lets the render travel. Second, a per-model label is only as strong as the uploader's right to apply it. A scan or a rip of a branded product uploaded by a stranger carries risk that a CC0 library built from its own staff and donating artists, as Poly Haven describes its collection, does not. Third, the format list is part of the license decision in practice: a model you cannot open, convert, or clean is not usable, whatever its terms say.

Source Notes: What Each Page Actually Says

Read these notes as a record of what was checked, not as a substitute for opening the page yourself at download time. Terms change, and the download date is part of your project record.

Poly Haven: CC0 Models With Redistribution Named

Poly Haven's license page covers HDRIs, textures, and 3D models in one statement: the assets are the work of its staff or of artists who donated or sold their work to the site, and all of them are licensed as CC0. The page summarizes CC0 in three points, covering any purpose including commercial work, no credit requirement, and redistribution, including sharing the assets with your own work or inside a product you sell. It also asks people who profit from the assets to consider supporting the site, which is a request, not a license condition.

The boundary on the same page is the website itself. Content that is not an asset, such as logos, avatars, example renders, and copy, stays protected, and the terms restrict scraping and data mining without permission. Download models through the site or its documented routes, save the license page with the project, and the record is complete.

ambientCG: CC0 With Raw-File Inclusion Stated

The ambientCG license page states that its assets are provided under the Creative Commons CC0 1.0 Universal License, and that this applies to the downloadable asset files and the material preview renders. Its summary lists copying, modifying, distributing, and performing the assets, even for commercial purposes, without asking permission, and it names including the raw files in a project, giving a video game as the example. Credit is not required, and the page supplies a short credit format naming the asset and the site for people who want to give it anyway.

For model work, the practical value is the bundle discipline. Materials and models arrive as sets of maps and geometry that belong together. A CC0 statement that covers the downloadable files as a set, with raw-file inclusion named, is the cleanest answer you can file for a scene that will be distributed.

Kenney: CC0 Game Assets, Confirmed on the Support Page

Kenney's support page answers the commercial question in its first entry: game assets on the asset pages are public domain under CC0 and may be used in commercial projects, with full details in the license file included with the download or on the asset page. The next entry covers credit: not required, with a name mention suggested for people who choose to give it, and a clear exclusion for the studio logo, which is reserved for official projects.

That combination suits prototypes and shipped indie work. The models are low-poly game pieces rather than photorealistic product geometry, so the fit question is stylistic. The license question is settled by the support page plus the license file in the pack. Keep both.

Quaternius: Pack Pages With Formats and a License Field

Quaternius publishes themed low-poly packs: characters, nature, furniture, vehicles, dungeons, and similar kits. Each pack page lists its contents with format labels; the Ultimate Nature Pack page checked for this guide lists FBX, OBJ, and Blend formats, animated and textured flags, and a license field. The downloads carry a CC0 1.0 license file.

Treat the pack page as the index and the included license file as the record. Download the pack, open the license file before you import anything, and file a copy with the project. If a pack page and its included file ever disagree, stop and use a different pack. That rule costs you one model and protects the whole project.

Smithsonian Open Access: Museum Scans Under CC0

Smithsonian Open Access is the strongest source in this guide for real objects: specimens, artifacts, machines, and historic items digitized by the institution. Its page describes the collection as available to download, share, and reuse without asking, across the Smithsonian's museums, research centers, libraries, archives, and the National Zoo, and its 3D content is presented through its 3D platform for viewing and download. Open Access items carry a CC0 designation.

Two checks still apply. First, confirm the specific item you take is an Open Access item on its record; a large institution's site also holds material under other terms. Second, a scan of a real object inherits the object's sensitivities. A specimen, a cultural item, or a famous machine may be free as a file and still be the wrong choice for a joke product or an implied endorsement. The license clears the file. Judgment clears the use.

Sketchfab: Read the System, Then the Model

Sketchfab needs two separate readings. For downloadable models, the license is the one the uploader selected, displayed on the model page. That can be CC0, a CC BY variant, an NC or ND combination, or a custom note. Apply the variant table in this guide to the label on that page, save the page, and credit exactly as the label requires.

For store models, the license agreement at sketchfab.com/licenses is a paid royalty-free grant. In substance, it is non-exclusive and single-seat. It forbids making the model available as a stand-alone file, sublicensing or selling it on, distributing a derivative that is too close to the original, and selling a print of the model or a slightly modified version. It also forbids putting the model into a logo, trademark, or other source identifier, and it reserves names, people, trademarks, and depicted designs to their owners, leaving releases to the buyer. Its editorial tier adds a hard limit: no commercial or promotional use, no implied sponsorship or affiliation, and use only in works that comment on, criticize, or report on the subject or an associated public-interest event. A store model can be the right buy for a single render. It is never a file you can hand to a client or bundle into a product for resale.

Formats: The File Check That Sits Next to the License

License work fails when file work fails. A model is only useful if your tools can open it, your renderer can shade it, and your delivery target can carry its weight. The Khronos Group describes glTF as a royalty-free specification for efficient transmission and loading of 3D scenes and models, built to keep both asset size and runtime processing low. Its core is a JSON description of the scene, which can be packed into a single binary file with the .glb extension, holding scenes, nodes, cameras, meshes, buffers, materials, textures, skins, and animations. Khronos also notes that glTF 2.0 was released as the ISO/IEC 12113:2022 international standard in 2022.

Use that as your delivery default and read the other formats by role.

glTF / GLB - the delivery format for web viewers, AR, e-commerce configurators, and most real-time engines. One GLB file carries geometry, materials, textures, and animation together, which also makes it the easiest bundle to audit for license records: one file, one source note.

FBX - a common interchange format in game and animation pipelines, often the format rigged characters arrive in (Quaternius and Kenney packs list it). FBX carries rigs and animation well. It is a production format, not a web delivery format; convert to GLB for the browser and keep the FBX as your working source.

OBJ - geometry and basic material references, with textures as separate files. OBJ has no rig or animation. It suits static props, print preparation, and scans (Smithsonian downloads have historically been offered in OBJ and glTF). The separate texture files are part of the licensed bundle: keep them together and do not lose the material file that links them.

Blend - the native Blender project file. A Blend file can contain modifiers, drivers, and scene setup that no export format preserves. Where a pack offers Blend alongside FBX and OBJ, take it as the editable master, then export your delivery format from it. Your modifications live in the master; the license note covers the pack as downloaded.

Scale, orientation, and polygon count - three silent defects ship with free models. Check the real-world scale on import (a chair that arrives 40 meters tall will break lighting and physics), check which axis is up before you rig or print, and record the triangle count against your target: a hero product model, a background prop, and a mobile AR model have very different budgets. None of this is a license question, and all of it decides whether the cleared model survives production. Pair heavy scenes with the performance rules in the web animation performance guide when the model sits inside an animated page.

Pick the Source From the Job

Start from the deliverable. The same model can be cleared for one job and wrong for the next.

Product renders and e-commerce

Use Poly Haven or ambientCG first. CC0 covers the render, the client handoff of a scene file, and a configurator build where the geometry ships inside the app. Convert the working file to GLB for any web viewer, keep texture resolution matched to the product's on-screen size, and file the license page with the job. A rendered still can then sit inside a sales page or a mockup presentation, where the mockup's own terms apply to the scene around your render.

Games and interactive scenes

Use Kenney and Quaternius for stylized work, Poly Haven and ambientCG for realistic environments. The license line that matters is raw-file inclusion, because a shipped game distributes the geometry to every player. CC0 states the answer. A CC BY model can also ship in a game, with its credit placed in the credits screen and its record kept with the build. An NC model cannot ship in a game you sell. An ND model cannot ship once you have adapted it, and adaptation is unavoidable in a real pipeline.

3D printing

Printing turns a file question into a product question. CC0 models may be printed and the print may be sold, subject to the depicted-rights check: printing a scan of a branded or designer object for sale is a product decision, not a file decision. The Sketchfab store license draws its line in the open, forbidding sale of a print of the model or a slightly modified version. For any model from a per-model page, read whether the label allows commercial use and adaptation before the printer warms up, and record the wall thickness, scale, and repair work you did as project notes.

Education, exhibits, and editorial scenes

Use Smithsonian Open Access. A real artifact scan carries context a generic prop cannot: the object exists, the institution digitized it, and the CC0 designation on its record clears reuse. Keep the item record with the scene file, name the institution in captions where your editorial standards call for it, and respect the sensitivity check above for cultural and human material.

A template, scene pack, or asset bundle you sell

This is the strictest job in the guide. Your buyer receives files. Only a license that allows redistribution inside a product answers it: CC0 as stated by Poly Haven (which names a product you sell), ambientCG (which names including raw files in a project), Kenney, and Quaternius, each verified from the license text or file you saved. A CC BY model can travel only with its credit and license notice intact inside your documentation. A store model cannot travel at all. When the answer is mixed, split the product: ship your own files, and link buyers to the source so they download the third-party model under their own record.

Client branding and identity work

Keep identity-critical geometry original or commissioned. No license in this guide makes a downloaded model exclusively yours, and the Sketchfab store agreement states the common rule in reverse, barring use of its models in a logo or trademark. A downloaded prop can furnish a brand's scene. It should not become the brand's mark. Record which scene elements are licensed and which are original in the brand style guide so the next designer inherits the distinction.

The File Checklist: Geometry, Rig, and Textures

Run this check on every model before it enters a client file. It takes minutes and produces the note your future self needs.

1. Name the bundle. List what arrived: mesh files and their formats, texture maps, material files, rig, animation clips, and any license or readme file. The bundle list is the unit the license covers.

2. Save the license record. Copy the license page or the included license file, the model page for per-model downloads, and the download date into the project folder. Name the folder for the source and the model, not for the project alone, so a later search finds it.

3. Open and measure. Import the model into a clean scene. Record scale, up axis, triangle count, and whether the geometry is manifold enough for your use (printing needs a closed, clean mesh; a render can tolerate more).

4. Check the rig and animation, if any. Play every clip. Note the root motion, the frame rate the clips assume, and whether the rig uses names your engine expects. A rig you have to rebuild is a schedule fact, not a defect to discover at integration.

5. Check the textures as images. Record each map's pixel dimensions and role (base color, normal, roughness, metallic, occlusion, emissive). Confirm the maps belong to this model and this license. A stray high-resolution photo texture inside a model bundle carries its own history; if its source is not the bundle's license, treat it as uncleared until you can name it.

6. Convert a delivery copy, keep the master untouched. Export GLB or your target format from a working copy. The original download, its license record, and its source page stay unchanged in the archive.

7. Run the depicted-rights pass. List any logos, product designs, artworks, buildings, or people the model represents. Decide, in writing in the project note, how each is used and why that use is descriptive rather than an endorsement.

The Traps, Named Plainly

The ripped game asset. Marketplaces and forums circulate models extracted from shipped games and films, sometimes relabeled with a friendly license. A label applied by someone who never held the rights grants nothing. Prefer libraries that describe how their models were made or donated, and walk away from any famous character, vehicle, or prop offered as free by a stranger.

The store model inside the client handoff. A team renders a store model into a scene, then sends the scene file to the client, geometry included. The license allowed the render. It did not allow the file transfer. Deliver flattened renders and built applications, and let the client license their own copy if they need the geometry.

The NC model in the monetized video. A model labeled NC appears in a tutorial, a stream, or a product video that earns money. Non-commercial means the use, not the file, decides. If money or client promotion is involved, NC is a no.

The ND model you already fixed. You rescaled, repaired, and retextured a model, then read the label: ND. The adaptation cannot be shared. Your repair work does not cure the label. Replace the model with a CC0 or BY equivalent and redo the fix. This is the cheapest version of that lesson you will ever get.

The credit that lives nowhere. A CC BY model ships inside an app with no credits screen, no about page note, and no documentation file. The credit requirement was the entire price of the model. Plan the credit location at download time.

The scan with a sensitive subject. A CC0 file can still be a human remain, a sacred object, or a cultural item whose display in your context is wrong. The Smithsonian record gives you the object's context. Read it, and let it inform the use.

A Worked Example: Clearing Models for a Furniture Store Demo

The following is a hypothetical example, written to show the checking order. No real client, store, or product is involved.

A designer is building a web demo for a small furniture store: a room scene in the browser, one printed catalog, and a downloadable scene file the store wants to give its own designer later.

1. Room set from Poly Haven. A sofa and shelving model under CC0. The license page covers any purpose, no credit, and redistribution including in a product. Verdict: cleared for the browser scene, the catalog renders, and the scene file handoff.
2. Floor material from ambientCG. A wood PBR set under CC0, with raw-file inclusion named on the license page. Verdict: cleared as the scene's floor, with the map bundle archived beside the model records. The textures guide file checks apply to the maps.
3. Character figure from a per-model page, labeled CC BY-SA. The figure would people the room scene. Credit is manageable, but the share-alike condition would follow an adapted version the store shares, and the store's contract promises it full control of the scene files. Verdict: not used. The designer replaces it with a CC0 figure pack from Quaternius, license file saved from the download.
4. A designer lamp from a store listing. The lamp is a current product with a living designer, sold under a store license that bars stand-alone distribution and trademark use. The store demo needs the scene file to travel. Verdict: not used in the downloadable scene. The designer models a generic lamp shape for the handoff version and keeps the branded lamp out of the demo entirely.

Total time: under an hour, most of it spent on import checks and one replacement download. The demo ships with a CC0 room, a documented material set, and a handoff file the store can actually pass on.

The Pre-Delivery Checklist

Run this before any scene, render, or model leaves your machine. It extends the pre-shipment pass in the design asset licensing checklist with model-specific steps.

• License named per model: every model has a recorded source page, license statement or included license file, and download date.
• Commercial scope confirmed: client work, ads, paid products, and distribution channels are inside the terms you hold for each model.
• Credit placed: any BY credit is in the deliverable's credits location, with creator, title, source, and license, and the client has seen it.
• File-travel rule honored: loose model files travel only where CC0 or the model's own label allows redistribution; store models stay inside finished work.
• Adaptation rule checked: no ND model was modified and shared; no SA adaptation ships without its license condition carried through.
• Bundle audited: texture maps, rigs, and clips inside each download are covered by the same record, or separately cleared and noted.
• Depicted-rights pass done: branded products, designs, buildings, and people in the scene are used descriptively, with no implied endorsement.
• Masters archived: the untouched download, the license record, and the dated project note are stored together, separate from working copies.

A 60-Second Decision Tree

For any free 3D model you are about to use, answer in order. Stop at the first no.

1. Can you name the license from the source itself? A library license page, a support page, an included license file, or the label on the model page. If none of these states the terms, the model is not cleared.
2. Does the license allow your exact use? A render, a shipped game, a print, and a file handoff are different uses. Match the use to the words you saved.
3. Will you modify it? If yes, ND is out, and SA conditions need a plan before you start.
4. Will the file itself travel? If a client, buyer, or player receives the geometry, confirm redistribution in the terms. Otherwise deliver finished work and link the recipient to the source.
5. Is credit required and placed? BY labels make credit the price. Decide the location now.
6. Does the model depict protected designs or brands? If yes, use it descriptively or replace it. The file license does not settle this question.

FAQ

Can I use free 3D models in client work?

Yes, when the model license allows commercial use. Poly Haven and ambientCG state CC0 terms covering any purpose, including commercial work. Kenney's support page confirms commercial projects for its CC0 game assets, and Quaternius packs carry a CC0 license file. Per-model downloads depend on the label on the model page: BY labels allow commercial use with credit, NC labels bar it, and store licenses allow it only inside finished work under their own agreement. Read the record for the exact model you download.

Do I need to credit the model creator?

Not for the CC0 sources in this guide. Poly Haven states credit is not required. ambientCG states credit is not required and provides a format for people who want to give it. Kenney states credit is not required for its game assets. Every Creative Commons license built on BY does require credit, in the manner the licensor specifies. Keep the creator name in your project note either way; it costs one line.

Can I sell a game, template, or scene that includes a free model?

Where the license allows the file itself to be redistributed inside a product, yes. Poly Haven states you can include its assets in a product you sell, and ambientCG states you can include raw files in a project. CC BY models can be included with their credit and license notice carried through. Store models cannot be distributed as stand-alone files or resold, and NC models cannot be used commercially at all.

Can I 3D print a free model and sell the print?

Under CC0, the file terms allow commercial use and adaptation, so printing sits inside the grant, subject to the depicted-rights check for branded or designer objects. Under the Sketchfab store license, selling a print of the model or a slightly modified version is forbidden in the agreement's own list. For per-model labels, an NC condition bars the sale and an ND condition bars sharing an adapted version. Check the label before printing for money.

What is the difference between a downloadable model license and a store license on Sketchfab?

A downloadable model's license is the one its uploader chose, shown on the model page, usually a Creative Commons variant. A store model's license is the paid royalty-free agreement on the Sketchfab licenses page, with standard and editorial tiers, a single seat, and a bar on stand-alone distribution. The two systems grant different rights for different models. The name of the site tells you nothing; the page for your model tells you everything.

Which format should I ask for, GLB, FBX, or OBJ?

Ask for the format your pipeline consumes and archive the rest. Khronos presents glTF, packed as a single GLB file, as the efficient delivery format for scenes and models, carrying meshes, materials, textures, skins, and animations in one file. FBX is the working format many rigged packs arrive in. OBJ is a static geometry format with separate texture files, common for props and scans. Take every format the pack offers; storage is cheaper than a return trip after a page changes.

A model page says free download but shows no license. What should I do?

Treat it as uncleared. A price of zero is not a license. Look for the label on the model page, a license file in the download, or a library license page that covers the collection. If none exists, choose a model from a source in this guide whose terms are stated in words you can save.

Sources Read for This Guide

• Poly Haven license page: https://polyhaven.com/license
• ambientCG license page: https://ambientcg.com/license
• Kenney support page: https://kenney.nl/support
• Quaternius pack pages, including the Ultimate Nature Pack: https://quaternius.com/
• Smithsonian Open Access: https://www.si.edu/openaccess
• Sketchfab license agreement: https://sketchfab.com/licenses
• Khronos Group, glTF overview: https://www.khronos.org/gltf/
• Creative Commons, CC0 and public domain tools: https://creativecommons.org/public-domain/cc0/

What to Read Next

• Free textures and patterns for commercial use - the material companion, covering the PBR map sets that shade the models in this guide.
• Free vector graphics for commercial use - the 2D counterpart, with SVG and EPS source and pack rules compared.
• Free mockups for commercial use - licenses for the scenes your rendered products will be presented inside.
• Image formats: SVG, PNG, JPEG, WebP or AVIF - how to export the stills and previews your 3D work produces.
• Design asset licensing checklist - the full pre-shipment review across fonts, icons, photos, mockups, video, and AI images.
• Free stock videos for commercial use - the same license discipline for moving images, including per-clip license labels.

This guide is maintained by the Lucky Graphics editorial team and reviewed when the sources above change their terms. It is general information about how 3D model licenses work, not legal advice for a specific project.