Skip to content
Browse documentation
DocumentationTemplates & licenses
Getting started

Templates & licenses

Choose a supported starting point and understand purchase access.

Supported template families

CompactEditor renders installed template families with their own layouts and supported settings. Public preview families include Aether, Underwater, Minecraft, Velocity, Keystone, Ember, Prism, and Frontier.

Ember, Prism, and Frontier use illustrated 2D artwork. Preview them publicly; paid editing and project ZIP backups remain locked until their separate BuiltByBit purchase verification is configured.

Hosted checkout supports all eight native design families for Minecraft stores when the required template access and Tebex merchant verification are complete.

Underwater uses the internal template identifier oasis. Existing projects keep their identifier, so a display-name change does not change their license or saved design.

Minecraft has an active customer purchase listing. Other preview designs may be coming soon. Available choices depend on the installed registry and your current access; a public preview does not grant a paid license.

BuiltByBit purchase access

Where a template requires a paid license, purchase it through its official BuiltByBit listing, then connect the purchasing account in CompactEditor. Verification checks access for that specific template.

A subscription to the optional AI add-on does not unlock paid templates. Access follows the verified usage rights for that template and the connected account. A separate download-access deadline does not automatically expire an existing usage right.

Find the template listings and pricing explanation.

An installed renderer, not arbitrary Twig execution

Templates in CompactEditor are supported application renderers. Importing a ZIP does not install or execute arbitrary Twig, JavaScript, or server code from an uploaded Tebex theme.

These are hosted CompactEditor designs; an installable Tebex theme download is not included. CompactEditor project ZIPs back up supported settings and catalog data for reopening in the editor.

Use the documented project import workflow for supported packages. Files from another theme may need adaptation rather than running unchanged. Read the import guide.