Requirements

Technical and development standards

Check the requirements for source files, compatibility, security, external services, and accessibility.

Updated

Download

Technical preparation

Customers must be able to open, edit, build, or run the supplied files as advertised, using the documented process. State any required software, services, or other resources clearly.

Technical quality

Core dependencies should use current, stable, and supported versions. Dependencies must be updated when their age, support status, or known vulnerabilities materially affect usability or security.

Production readiness

Where an item is installed, built, or run, it must work from the download package using the documented process. Where a production build process exists, use it and include production-ready files. Do not rely on development-only runtimes, preview servers, browser-based compilers, or other tooling identified as unsuitable for production.

Code, markup, stylesheets, configuration files, and structured data must use valid syntax. Resolve avoidable warnings, debugging output, unresolved placeholders, and errors that occur during normal intended use before submission.

Design files, 3D scenes, presentation decks, and other creative source files must open cleanly in the represented software, remain editable as advertised, and include the resources necessary for normal use. Resolve missing links, fonts, images, textures, media, plugins, substitutions, and other dependencies, or clearly disclose and document any resource the customer must obtain separately.

Source quality and maintainability

Code, design documents, 3D scenes, presentation decks, and other source files should be organized, understandable, maintainable, and suitable for customer use. Customers should be able to identify the package structure and work with the source files using the documented process.

  • Formatting, indentation, naming, file organization, and comments should be reasonably consistent and follow established practices for the language, framework, or platform.
  • Layers, objects, pages, components, styles, masters, materials, rigs, and similar editable structures should be named and organized appropriately for customer use.
  • Avoid unnecessary duplication, dead code, inaccurate comments, and temporary development workarounds.
  • Follow reasonable practices for maintainability, performance, error handling, and dependency management.

Compatibility and requirements

Compatibility selections, when offered for the category, and disclosed requirements must give customers an accurate understanding of the technologies they can work with and anything they need to use or customize the item.

Each compatibility selection is a customer-facing claim. Select only options that materially describe the delivered item and have a reasonable basis in testing. An item does not need to support technologies, platforms, formats, or tools that are not represented as compatible.

Compatibility selections

Compatibility selections must describe the customer-facing source or working formats provided in the package, not every technology that appears somewhere in the implementation.

Some categories do not offer compatibility selections. When no selections are offered for the chosen category, none are required. The item description and documentation must still identify its actual working formats, required software, and other material requirements.

Do not select a technology solely because it:

  • Is an incidental dependency.
  • Appears only in compiled or generated output.
  • Supports an auxiliary feature.
  • Is used internally by a build tool.
  • Is used only to operate the live preview.

For example, a PHP contact-form script does not by itself make an otherwise front-end template compatible with PHP.

Select HTML, CSS, or JavaScript only when the package includes those as source formats customers are expected to work with directly. Do not select HTML merely because a framework renders HTML or because the package contains generated output. A customer looking specifically for an HTML template should not be misled by the selection.

Versions and tested environments

Provide version information where requested. Use the narrowest version or range that accurately represents compatibility. Ranges such as 5.x or 5.3.x may be used when there is a reasonable basis for expecting the item to work throughout the represented range.

For applicable web items, select only browsers in which the item has been tested and its advertised functionality works as intended. Customers should be able to rely on each selected browser as a supported environment.

Web Games category

Test core gameplay and every advertised input method in each selected browser and represented device type. Do not claim keyboard, mouse, touch, gamepad, desktop, or mobile support unless the game remains usable as intended with that method or environment.

Customer requirements

Clearly disclose any software, service, account, plugin, font, API, hosting environment, build tool, or third-party resource required to install, open, edit, build, host, or use the item. Distinguish required resources from optional ones and identify the part of the item or workflow to which each requirement applies.

Requirements that materially affect whether a customer can use the item must be disclosed in the item description before purchase. This includes any additional purchase, paid subscription, usage-based charge, account registration, API key, quota, regional limitation, or service plan. Material limitations of a free plan must also be disclosed when they affect advertised functionality. Detailed setup instructions may be provided in the documentation.

Security, privacy, and external connections

Items must be safe to use. They must not contain harmful behavior, real private or sensitive data, active credentials, or other secrets not intended for distribution.

Material external connections and any collection or transmission of data must be clearly disclosed.

Customers must be able to understand when an item connects to an external service, what the connection does, and whether it collects or transmits data.

Security and sensitive data

Items must not contain malicious code, backdoors, cryptocurrency miners, deceptive behavior, or code intended to gain unauthorized access, conceal harmful functionality, or interfere with a customer's systems or data.

Do not include:

  • Real customer or personal information, private communications, production database data, or other private content.
  • Active credentials, passwords, API keys, access tokens, or reusable default passwords.
  • Private URLs or other secrets not intended for customer distribution.

Example data must be fictional and safe to distribute. Placeholder credentials must be nonfunctional and clearly identified as values the customer must replace.

External connections and data collection

External connections must serve a legitimate item-related purpose. Material connections must be accurately disclosed and documented. This includes analytics, telemetry, tracking, remote APIs, externally hosted assets, remote configuration, update services, license checks, and connections to creator-controlled servers.

Documentation must identify the purpose of each material connection, whether it is required or optional, and the types of data it sends or receives. Explain how optional connections can be configured or disabled where applicable.

An item must not secretly collect or transmit customer, visitor, project, or usage data. Any collection or transmission of data must be appropriate for the advertised functionality, clearly disclosed, and lawfully implemented. Do not collect more data than reasonably necessary for the stated purpose.

Remote code and services

Do not load executable code or introduce material functionality from a remote source without clear disclosure. Remote code, configuration, or services must not be used to conceal functionality or change the item in a way that a customer would not reasonably expect.

If important functionality depends on an external or creator-controlled service, disclose it as a requirement and explain the dependency, its limitations, and what happens if the service becomes unavailable. Connection failures must not expose or corrupt customer data or leave the item in an unsafe state.

Installation, updates, and data safety

Installation, import, migration, update, and removal processes should be safe and appropriate for the intended customer. They must not unexpectedly overwrite content, reset configuration, remove files, modify unrelated data, or perform another destructive action without clear notice and confirmation.

Document backup requirements, permissions, database changes, irreversible steps, and other material risks before the customer performs the action. Updates should preserve customer content and configuration where reasonably expected, or clearly explain any breaking change and the steps necessary to complete the update.

Sample content, import files, and setup tools must work as documented and must not depend on private files, temporary URLs, or creator-controlled resources that are not disclosed and intended to remain available.

Accessibility and inclusive use

Items should follow reasonable accessibility practices appropriate to their format and intended use. Where applicable, this includes semantic structure, keyboard-accessible controls, visible focus states, associated form labels, understandable validation messages, alternative text, sufficient contrast, and text that remains legible when resized.

Wrapmarket review is not a complete accessibility audit. Creators remain responsible for testing the item and for accurately describing any accessibility support or limitations.

Was this article helpful?