Frequently Asked Questions
This page answers common questions about EmoteLab. If you don't find what you're looking for, consider asking in the Steam Community or Discord.
General
Q: Can you add a feature/component/part/animation to the app/model?
A: We welcome and collect feedback on new features, components, or animations. However, we do not commit to implementing requests from individual users or for single-use scenarios. We cannot guarantee that any specific feature, component, or animation will be added, nor can we provide a definite timeline for updates. Whether new content is introduced depends on technical feasibility, aggregated feedback across platforms, and the overall value it provides to the majority of users.
We will continue to improve the product based on community feedback, but we do not accept requests for custom features/components/part/animations, nor can we make commitments to fulfill individual requests.
Built-in Assets
Q: Can I take commissions for creating assets for others?
A: Yes! You’re allowed to take commissions and get paid to create assets (such as character data or texture images) for others using EmoteLab.
When delivering character data to a client, it’s recommended to provide the saved character with unpacked texture images (not a packed texture atlas). This helps ensure better compatibility, since texture atlas layouts may change when the model is updated.
Q: Can I make emotes for others and sell or gift them?
A: Yes! You can create emotes for other people and either sell them or gift them.
As long as:
- You only share or sell the final emote files, not the unedited built-in assets themselves (for example, the unedited image of the notepad).
- You don’t claim or imply that you personally created the original character designs or animations.
If you don’t disclose that EmoteLab was used (and that this is a template-based workflow), clients may later notice that animations or motions look identical to other users’ emotes, which can cause confusion or disputes. - In public or client-facing situations, clearly state that the emotes were created using EmoteLab.
Using EmoteLab emotes on Twitch, Discord, YouTube, merchandise, and similar platforms is totally fine under these rules!
Q: Can I make merchandise (for personal use, gifts, or selling) using output images created with EmoteLab?
A: Yes! You may use images exported from EmoteLab to create merchandise for personal use, as gifts, or for sale.
However, please make sure you follow these rules:
- You may only use the final exported output images (such as PNGs or GIFs). You may not distribute or reuse EmoteLab’s built-in assets in a raw or extractable form.
- You don’t claim or imply that you personally created the original character designs or the image.
- In public or client-facing situations, clearly state that the emotes were created using EmoteLab.
If you commissioned another artist to create custom textures or other assets for use with EmoteLab, you are responsible for following that artist’s license terms and usage rules. This includes whether the assets may be used for merchandise, commercial sales, or redistribution. When in doubt, please check directly with the artist.
As long as these conditions are met, using EmoteLab output images on merchandise (such as prints, stickers, apparel, or similar items) is allowed.
Q: Can you review my project and confirm whether my use is allowed?
A: No. The End User License Agreement (EULA) already defines the rights and permissions granted to you. If your intended use complies with the applicable license, you do not need additional permission or confirmation from us. Your rights come from the license itself, not from a separate approval message.
Because of this, we do not provide case-by-case reviews or project-specific approvals. Users are responsible for reading the license and determining whether their own use complies with its terms.
There are also practical reasons why individual projects cannot be reviewed reliably:
- A project may change or expand after an initial inquiry, so the information provided may no longer reflect the actual use.
- A project description may not contain all the information needed to evaluate every relevant aspect of the license.
- It is not practical to review individual projects in detail or keep track of every project for which permission was previously requested.
- Providing approval based on a limited description could create confusion if the actual project later differs from what was described.
If you have a question about the meaning of a specific term or provision in the license, you are welcome to ask for clarification. However, we do not provide project-specific instructions on how to modify or structure a project to comply with the license, and we do not provide case-by-case determinations or approvals.
Please review the applicable license and evaluate your intended use based on its terms. If you need legal advice or a formal assessment of a specific situation, please consult a qualified lawyer.
Usage
Q: Is there a more ergonomic way to copy-paste colors?
A: you can drag and drop the source part onto the target part
Support
Q: How do I report a bug or suggest a feature?
A: You can share feedback and report issues through Discord or the Steam Community. For detailed bug reports, please include your system information and steps to reproduce.