Guide

Can I resell, redistribute, or open-source an item?

Learn what you can share privately for project work and why the Standard License and its add-ons prohibit distributing the item for others to reuse.

Updated

Download

Quick answer

Under the Standard License, you can release a permitted end product. You cannot sell, give away, or open-source the item or a reusable version of it for others to use in their own projects. Neither add-on changes that rule.

This guide explains the Standard License and its add-ons. For a migrated license, you may also choose the original license terms. Check which terms apply to your license before deciding what you may redistribute or publish.

A finished end product is different from a reusable item

The license lets you use an item to create a permitted end product. It does not give you a general right to distribute the item files, a modified version of the item, or an extracted collection of its components for other people to reuse.

The Commercial Add-on expands selling and paid-access rights for an end product. The Unlimited Projects Add-on expands the number of end products. Neither removes the redistribution and reuse restrictions.

Private access for project work

You can keep licensed files in a private repository. A contractor working on your behalf may access the files they need to develop, test, or maintain your end product. They may use the item only for that work, and you remain responsible for how they use it.

You can also give a coding assistant private access to the files it needs. A hosted assistant's terms and settings must keep the files private to your project and exclude them from model training. Read more about using AI tools with a licensed item.

Examples of prohibited redistribution

  • Purchasing a license for a website template, changing its colors, and selling it as your own template.
  • Converting an item to another framework and distributing the result as a reusable starter or UI kit.
  • Putting the downloaded item or a reusable derivative in a public source repository.
  • Giving away extracted components as a free asset pack.
  • Offering a builder or generator that lets users obtain reusable outputs based on the item.
  • Uploading the item to a marketplace or asset library, whether access is free or paid.

Making a product free does not bypass these restrictions.

Open source is not an automatic exception

The current terms prohibit making the item or a reusable derivative available as open source, or under another arrangement that allows the prohibited reuse or redistribution.

An item being built with an open-source framework does not make the creator's template, design, or other item files open source. Review the third-party component terms separately; they do not replace the rights and restrictions for the item itself.

If you want to publish a project's source, identify which files contain the item or a reusable derivative before proceeding. Do not assume that placing a license notice in the repository makes redistribution permitted. Contact Wrapmarket support if you need help assessing a particular release.

Redistribution restrictions for paid end products

The Commercial Add-on lets you sell an end product or charge for access to it. You still cannot provide the item files, extracted assets, or builder outputs for customers to reuse independently of that end product.

Check what customers pay for and whether they can obtain reusable item files. See SaaS, subscriptions, and paid memberships for the first question and the full License terms for the restrictions.

Client work has its own limits too

The license permits client work, but that permission is not blanket authorization to transfer the license or give a client reusable files for unrelated projects. See using an item for client work when planning a handoff.

Was this article helpful?