Table of Contents
All files submitted in the VideoHive Apple Motion Project File category must be prepared for commercial use. This article outlines all the requirements to ensure that your Project File meets the expected standards which will help us approve your project quicker.
We are aware that many people learn how to use Apple Motion by watching or reading tutorials but we do not allow files to be uploaded that were created based on one or more tutorials.
Of course, if you learn a technique from a tutorial and then use that technique while integrating it into a greater project, made with mostly original work it can still be accepted.
- Any project files submitted that appear to be based completely or closely on a tutorial will be rejected.
- Project files which were created to replicate or copy another person’s existing work will not be accepted.
- Apple Motion Project Files cannot make use of third-party plugins.
Main File - Folder Structure
All items should follow a clean and organized folder structure as explained below:
- Your project root directory should contain:
- Project file(s)
- Help documentation
- Asset(s) and footage sub-folders
- File/Folder names - Provide meaningful names to the files and folders to guide customers through your project directory.
- Any element within your Project File that needs to be changed by the customer should be easily editable and located within its own dedicated composition.
Assets are photos, illustrations, videos, code or music that may be a part of your item or item preview. It is very common to include assets in your Apple Motion Project File that need to be included in your zip folder and distributed to your customers.
- If you are planning to include assets from an outside source, check if those assets are properly licensed. For more information on the asset usage, please read this article.
- Ensure that all the assets are placed in the correct folder and linked properly before saving your project. Replacing or relocating asset files after saving your project file could result in “Missing File” errors.
- Any asset used in your preview which cannot be included in your zip file should be replaced with placeholder assets to prevent missing file errors. You can use the following in your file’s preview and these can also be included in your zip folder as placeholders:
- Any assets used in your preview that cannot be included in your zip file should be replaced with placeholder assets to prevent missing file errors. Customers can easily replace the placeholder assets with their own assets when they edit the project. You can use the following in your file’s preview, and these can also be included in your zip folder as placeholders:
Video assets can be provided in two ways, either as a video file or as an image sequence. If you choose to provide video files they must be provided within a Quicktime MOV container and must use one of the following encoding formats:
- Photo JPEG
- PNG + Alpha
- Apple ProRes 422
- Apple ProRes 422 HQ
We accept image assets in any format that is supported by Apple Motion.
Audio assets must be provided in one of the two following formats and should be free from any audio watermarks:
Compositions containing elements that require customization should be clearly named and organized in such a way that customers can quickly identify all compositions and make changes efficiently.
All Project Files on VideoHive are required to include documentation that guides customers through the customization process. As we require documentation to cover certain topics, it is very important to read this article and get yourself familiarised with our documentation requirements.
Failing to include a valid help file can result in a soft-rejection by our review team.
Ready to Upload
Once you have got your Apple Motion Project File ready to sell, you should follow this guide to preparing your item for upload.