FAQ

Questions

Is it really free?

Yes. Unapp is licensed GPL v3, with no paid tier, no locked patterns and no "pro" upsell inside the theme. Use it on as many sites as you like, for clients or for yourself, and modify it however you want.

Do I need a page builder?

No, and you should not use one. Unapp is built for the Site Editor with core blocks only. Elementor, Divi, WPBakery and the rest bring their own layout engine, which will fight the theme's own. If you want a page builder, use a theme designed for one.

Will it work with my plugins?

Anything that follows normal WordPress conventions, yes. Contact forms are explicitly supported — the theme detects ten form plugins and styles whichever you have. WooCommerce has its own templates. The theme registers no post types and takes over no admin screens beyond its own Starter Sites page.

Can I use it on a client site?

Yes, including commercially. GPL v3 permits it and there is no per-site licence to buy or track.

How do updates work if it is not on WordPress.org?

Exactly like a directory theme: through Dashboard → Updates. Unapp uses the Update URI mechanism WordPress added in 6.1. See updates and privacy for precisely what the check sends, and how to turn it off.

Should I use a child theme?

Only if you are editing theme files. Most customisation — colours, fonts, spacing, templates, headers, footers — happens in the Site Editor and survives updates on its own. If you do need PHP or CSS changes, a ready-made child theme is in the repository.

I am on Unapp 1.x. Can I upgrade?

Not in place, no. Version 2.0 was a complete rewrite: 1.x was a classic theme built on the Epsilon framework with Customizer sections and Bootstrap 3; 2.x is a block theme with none of that. Your 1.x content was stored in Customizer settings that no longer exist.

The practical route is to install 2.x on a staging site, apply a starter, and move your text across. Your posts and pages are untouched by any of this — it is the homepage sections and theme options that do not carry over.

Is it translation ready?

Yes. Every string, including all the text inside patterns and templates, goes through the unapp text domain, and a .pot file ships in languages/. It is RTL-ready too.

Does it work with multilingual plugins?

Patterns are ordinary block content once inserted, so WPML, Polylang and TranslatePress handle them the way they handle any page. The theme's own interface strings come from the .pot.

How do I report a bug?

GitHub issues for bugs, the Colorlib support forum for help using it. Include your WordPress version, PHP version and which starter you applied.