Template submission guidelines.

Pass the WordPress test data

Your template should render cleanly against the standard WordPress unit test data, with no visual problems.

• Posts display correctly: title, body, comments, comment form and post meta all render.
• Posts appear in the right order; pagination and the Read More link work.
• Search results display, with a clear notice when there are none.
• Sticky posts and all post formats are styled in index and archive views.
• Both Tag and Category taxonomies are supported; missing content never breaks the layout.
• Floats are cleared (especially around thumbnails) and long strings don't overflow.

License every asset you include

You need the correct commercial-redistribution license for everything bundled in the template, including preview-only assets.

• Verify attribution requirements for every asset.
• Clearly document any developer licenses for the themes or plugins you require.

No malicious content

Templates must be free of malware and viruses. InstaWP reserves the right to remove items or accounts and notify affected customers if a security threat is found.

Include a help file

Every template ships with documentation so a buyer can get going on their own.

• Concise instructions for installation, customization and use, plus any further details.
• Details and links to any assets that need crediting.
• English language, in PDF or HTML. Screencasts can supplement the text, but not replace it.

Write a clear item title

Keep it informative, concise and professional, with only the most relevant information. Specify the base theme, and if you're a new seller, put your brand name at the start.

Pick the right category

Choose the category that accurately represents the template's purpose or functionality. Don't use a misleading category to chase visibility.

Use high-quality images

Show the UI and key features clearly and accurately.

• Format PNG or JPG, max 5 MB each.
• A 4:3 aspect ratio is recommended.

Describe it well

Write a comprehensive but concise description that highlights the key features, benefits and use cases, and clearly state any requirements or dependencies for installation, configuration or use.

Stay legal

Follow applicable laws and copyright rules. Don't infringe anyone's intellectual property, including trademarks, logos or copyrighted material, and clearly state your licenses and permissions.

Offer support and updates

Tell buyers how to get help, whether you provide ongoing updates and bug fixes, and include your contact details in the documentation.