Why Linguise Does Not Translate Tilda Dynamic Content
In this article: why Linguise does not translate Tilda dynamic content, what architectural reason is behind it, and how it affects real projects.
Agencies often choose Linguise for Tilda because it is positioned as a "proxy translator." In practice, it turns out: static pages are translated, but forms, carts, and pop-ups are not.
What is dynamic content in Tilda
Tilda generates some content not when the page loads, but during user interaction. This includes:
Forms (input fields, placeholders, validation error texts)
Online store cart (product names, buttons, messages)
Pop-up windows (popup blocks)
Notifications after form submission
Dynamically Loaded Content
All this content is generated by JavaScript on the browser side — it is not in the original HTML that comes from the server.
Why this is a problem for Linguise
Linguise works as a proxy — it intercepts the server's HTML response and translates it. But the HTML that Linguise receives does not contain dynamic content. It will appear later, when the browser executes JavaScript.
Linguise sees the form as an empty container. The text inside the form — placeholders, field labels, submit button — appears after Linguise has processed the page.
Result: the form on the website remains in Russian on all language versions.
How it looks in practice
A user from Germany opens the German version of the site. The page is translated — headings, texts, navigation in German. They reach the application form — and see Russian text: "Enter name", "Your phone", "Send".
For some projects, this is critical. The form is a conversion point. A user who sees an unlocalized form feels a discrepancy and trust decreases.
Tilda generates form content using its own JavaScript. This JS executes in the browser and inserts text after the proxy has processed the server's response.
To intercept and translate this content, the proxy must either: - Execute JavaScript on the server (SSR) before delivering the page to the user, or - Have a special integration with Tilda and know exactly how it generates dynamic blocks
Linguise does neither. Therefore, dynamic content remains untranslated.
What Works Differently
A proxy that performs full server-side rendering receives the page with JS already executed — including all forms, carts, and pop-ups. The full version of the page is translated, not just static HTML.
If your site has at least one form, cart, or pop-up — check the tool's translation on these elements, not just on static texts.
Do a test run: open the translated version, fill out a form, add an item to the cart. If you see the original language, the dynamic content is not being translated.
Frequently Asked Questions
Why doesn't Linguise translate forms on Tilda?
Linguise works as a proxy and translates the server's HTML response. Forms on Tilda are generated via JavaScript in the browser — after the proxy has processed the page. Therefore, the text inside the forms remains in the original language.
Which proxy fully translates Tilda dynamic content?
A server-side rendering proxy executes JavaScript before delivering the page to the user and translates all content — including forms, shopping carts, and pop-ups.
Can I check the dynamic content translation before purchasing a subscription?
Yes. Most services provide a demo or trial period. Check the form and shopping cart specifically — this will quickly show the tool's limitations.
Does an untranslated form affect conversion?
Yes. A form is a conversion point. A user who sees unlocalized elements at the final step feels a mismatch and is more likely to leave without submitting an application.
Check the translation of forms and shopping carts
Multify translates Tilda dynamic content — forms, shopping carts, pop-ups. Check it on your website's demo.