Licensing

Effective date: [31-01-2026]

This Licensing page (“Licensing Terms”) explains how digital content (“Items”) from GodotAsset.market may be used. It applies to both paid and free downloads unless stated otherwise.

These Licensing Terms should be read together with: Terms of Service and EULA (/terms-of-service), Refund Policy (/refund-policy), Author Terms (/author-terms), and (where applicable) Free Items Policy (/free-items-policy).

1) Key concept: product license + marketplace rules

Each Item may have a license shown on its product page and/or included inside the download (e.g., LICENSE.txt, EULA, README). That license (“Product License”) is the primary source of usage rights for that specific Item.

License priority

(1) Product page License (as displayed at the time of purchase/download),
(2) License included in the downloaded files,
(3) These Licensing Terms (platform-wide rules and baseline restrictions).

If there is a conflict, we apply the stricter rule unless the Author explicitly states a different priority on the product page.

2) Definitions

Item – any downloadable digital content (assets, plugins, tools, templates, shaders, audio, UI kits, etc.).
End Product – your final game/app shipped or delivered to end users (commercial or free).
Source Files – editable/original files (e.g., .blend, .psd, .kra, .svg, raw WAV, project templates, plugin source code).
Team – your employees and contractors working on your End Product or internal production.
Buyer – the person or legal entity/company that purchased the license.

3) License options: Regular vs Extended

Some Items offer two license options shown at checkout: Regular and Extended. The chosen option is part of your purchase and determines the scope of permitted use.

Regular license (one project)

Permits use of the Item in one End Product (one game/app/project).
Internal sharing is allowed only within your Team working on that End Product, only as needed for production.
If you want to use the same Item in a different, separate End Product, you must purchase another Regular license (or choose Extended if available).

Extended license (unlimited projects)

Permits use of the Item in unlimited End Products under the same Buyer (same individual or the same legal entity/company).
Internal sharing is allowed within your Team only as needed for production.
Extended does not allow redistribution/resale of the Item as a standalone product and does not permit “asset pooling” across unrelated entities.

What counts as “one project”

Different platform builds/ports of the same game/app (e.g., Windows/Linux/macOS releases) are typically considered the same End Product.
A sequel, a separate game/app, or a substantially different product is a different End Product.

If an Item’s product page or included license defines “project” differently, that Product License may override this section.

4) License grant (baseline)

Unless the Product License says otherwise, when you purchase or download an Item you receive a non-exclusive, non-transferable, revocable license to use the Item, subject to these Licensing Terms and the Product License.

Ownership stays with the Author (and/or other rights holders). You do not acquire ownership of the Item, only usage rights under the applicable license.

5) Allowed uses (baseline)

Unless restricted by the Product License, you may:

Use Items in End Products (games/apps) for personal, educational, and commercial purposes.
Modify Items to fit your project (e.g., edit textures, adjust meshes, change code, re-mix audio).
Combine Items with other content in your project.
Share Items internally with your Team members working on the same End Product, only as needed for production.

6) Prohibited uses (baseline)

Unless explicitly permitted by the Product License, you may not:

Redistribute or resell an Item (or substantially similar content) as a standalone product, including re-uploading to other stores, repositories, or file-sharing services.
Share Source Files publicly (or with third parties outside your Team), including “asset dumping” and “project sharing” that exposes the raw files.
Use Items to create competing asset packs or marketplaces (including “kitbashing” where the original content remains recognizable).
Remove or bypass license checks, activation mechanisms, watermarks, or other protection measures included with an Item.
Use Items to distribute malware, backdoors, spyware, miners, or harmful code.

7) Team sharing, contractors, and studios

Items may be shared with your Team members only for the purpose of building your End Product. Team members may access Source Files only to the extent necessary to work on that End Product.

Contractors/freelancers: you may provide access to an Item if they are working for you on the End Product. They must delete Source Files when the work ends.
No “asset pooling”: you may not buy one license and share it across unrelated teams, unrelated companies, or multiple clients.
Client work: if you are a contractor delivering work to a client, the correct Buyer is typically the client (or you must ensure the Product License allows your use for client delivery).

8) Distribution inside your shipped game/app

In general, you may ship Items as part of your End Product (including compiled code, baked textures, exported meshes, and other assets included in the final build).

However, you must not intentionally distribute Source Files as a separate deliverable unless the Product License permits it.

9) Plugins, tools, and code Items

Some Items include editor plugins, tools, scripts, or source code (“Code Items”). Unless the Product License says otherwise:

You may use Code Items in your projects and internal pipelines.
You may modify Code Items for your own use.
You may ship code as part of your End Product if it is required at runtime.
You may not repackage and distribute the Code Item as a competing plugin/tool (including re-uploading modified versions) unless explicitly allowed.

10) License keys, activation, and verification

Some Items may require license keys, online verification, or account-based activation. You agree not to bypass or interfere with license verification mechanisms, and not to share license keys outside the scope permitted by the Product License.

11) Open-source and third-party components

Some Items may include third-party components (for example: fonts, libraries, or open-source code). Those components may be governed by their own licenses and notices, which can add requirements (such as attribution) or limitations.

When third-party license terms apply, you must comply with them. If the Product License and third-party license conflict, the third-party license controls the third-party component.

12) Support Periods (optional add-on)

Some Authors may offer an optional paid add-on called a Support Period. This is an additional service layer that provides access to author support for a defined time window (for example: faster responses, troubleshooting guidance, and feedback on bug reports).

Important clarification

Support Period is not a subscription.
Support Period does not grant additional licensing rights.
Support Period is separate from updates. Purchasing support does not automatically guarantee future updates, and not purchasing support does not automatically remove access to updates that the Author provides for the Item.

What support typically includes

Help with installation and configuration of the Item.
Troubleshooting and guidance for reproducible issues.
Clarifications about documented features and intended workflow.

What support typically does not include

Custom development work, bespoke features, or consulting beyond reasonable assistance (unless explicitly offered as a separate service).
Guarantees of bug fixes, new features, or compatibility with every project setup.
Support for issues caused by unrelated third-party assets, modified engine builds, or heavy project-specific customization.

The exact support scope (response expectations, channels, limitations) may be stated on the Item page. Support is provided by the Author.

13) AI training and dataset usage (baseline rule)

Unless the Product License explicitly allows it, you may not use Items (or substantial parts of them) to train, fine-tune, or build datasets for generative AI models intended to reproduce or generate similar content.

If an Author allows AI training, they must state it clearly in the Product License or product description.

14) Support, updates, and compatibility

Unless explicitly stated on the product page, Authors are not required to provide support, custom work, or guaranteed updates. Compatibility (engine version, OS, render pipeline, dependencies) is defined by the product page and documentation.

15) Enforcement and termination

Violations of these Licensing Terms or a Product License may result in actions such as removal of access, account suspension, and other remedies available under applicable law.

If your license is terminated due to a material breach, you must stop using the Item and delete Source Files in your possession/control, except where mandatory law provides otherwise.

16) Plain-language note

These Licensing Terms are designed to be understandable. They do not replace legal advice. If you are publishing as an Author or licensing to a studio, you should consider professional legal review.