Frequently asked questions
MIT licensing, commercial use, framework support and migration paths.
Yes. All Templatical packages are open source under MIT, with no usage caps or per-seat fees.
Yes. MIT permits commercial use, including paid SaaS, internal tools, on-premise software and agency builds. Keep the copyright and licence notice.
All published Templatical packages, including editor, core, media library, renderer, types, quality tools, importers and AI kit, are MIT-licensed.
Hosted builders give you a turnkey editor and a stocked template catalog, but the editor sits behind their pricing — custom blocks, white-label, advanced theming and custom merge-tag syntax usually need a higher tier, and most meter your end users or your exports. Templatical is the embedded, self-hostable opposite: your customers see your brand, nothing is billed per seat, and you ship MJML you can render anywhere. If you mainly want a hosted editor with a large pre-built template library, a SaaS builder will be faster. Sourced side-by-side comparisons with Beefree SDK, Unlayer, Stripo, Topol, Chamaileon, Easy Email Pro and GrapesJS are linked in the footer.
No. The editor renders a small footer credit by default, but it's opt-out — pass branding: false to init() to hide it. There is no forced header logo or other attribution surface in the editor UI.
Templatical works in React, Svelte, Angular, Vue, and vanilla JS. The published package is fully self-contained — Vue is bundled inside, so consumers install one package with zero peer dependencies and mount the editor with a single init() call into any DOM element.
Run npm install @templatical/editor and mount the editor with one init() call. To convert templates to MJML, also install @templatical/renderer; it is optional. The installation guide on docs.templatical.com covers pnpm, yarn, bun and the CDN build.
We provide free, MIT-licensed converters for Beefree, Unlayer, Stripo, Topol, Chamaileon, Easy Email Pro, HTML and MJML. They import your existing templates directly and handle block mapping, style preservation, and merge tag conversion automatically — and each returns a report of anything that needs a manual look. The docs carry a migration guide per source format.
Yes. List the languages in the localization option of init() and authors add language versions from the Languages menu: one shared block tree, with each language’s text, property overrides and hidden blocks. A missing translation shows the default language’s text. Translate fills a version through the TranslationProvider you pass as the translation option, which can call an LLM, DeepL or a translation management system, and renderToMjml renders one language when you pass its locale. Subject lines stay with the system that sends the email, and column structure is shared by every language.
Only to your own backend. The SDK runs entirely in the browser — no telemetry, no remote calls, no analytics. A template leaves your app only through a provider you configure: when it is saved, sent as a test, sent with an AI request, which your backend passes to the model you choose, or sent for translation, which your backend passes to the translation service you choose.
No. The editor mounts inside a Shadow DOM by default, so host stylesheets stop at the boundary. Your body font-family, your design system's box-sizing reset, your framework's preflight — none of them reach the editor. If you want your theme to apply, set --tpl-user-* CSS variables on the container; they inherit across the shadow boundary. You can opt out with shadowDom: false if you need a light-DOM mount.
No. The SDK is standalone and MIT-licensed. Every storage feature uses a provider you implement on your own backend; there is no managed backend from Templatical.
For bugs, open an issue; for questions and ideas, open a discussion — both on GitHub, so the answer stays searchable for whoever hits the same thing next. Email hi@templatical.com for licensing and commercial questions, or anything you would rather not ask in public. Security reports have their own private channels, listed in SECURITY.md.
Didn't find your answer?
Ask the community on GitHub Discussions, or start with the installation guide in the docs.