Which File Formats Does Seatext Support for Editing Translations in Tilda?

Seatext supports plain text, JSON, and CSV files when you edit translations in Tilda. Use plain text for quick copy fixes, JSON for structured translation keys, and CSV when reviewers want to see languages side by side.

The translation layer itself runs through a small JavaScript snippet installed on your Tilda site. Once the snippet is connected, Seatext can serve translated text without changing your design. The file format becomes important when you import, export, or edit translation content outside the visual editor.

Why the file format matters for Tilda translation edits

Tilda stores content in blocks. If you only change a headline in the Tilda editor, that one block changes. Seatext works above that layer and can rewrite page copy to match visitor intent or language.

The format you choose decides who can edit, how clean the text stays, and how much work it takes to keep translations in sync. Plain text is easy but loose. JSON is precise but unforgiving. CSV is friendly for non-developers but fiddly with commas.

Whatever format you choose, save the file with UTF-8 encoding when your translations include accents or non-Latin characters.

How the Seatext-Tilda connection works

You install Seatext by pasting a JavaScript snippet into Tilda. That snippet links your domain to your Seatext account. The AI stays inactive until the connection is confirmed.

For all pages, use Site Settings, then More, then HTML code for the head section, then Edit code. For one page, add a T123 block and paste the code into the Content editor.

After pasting the code you must save and publish the site. Publishing is not optional; the live page needs the updated code before Seatext can translate anything.

Step-by-step: connect Seatext and edit translations in Tilda

1. Create a Seatext account for the live domain.
2. Copy the JavaScript code from the Seatext dashboard.
3. In Tilda, open Site Settings and paste the code into the field labeled Edit code inside HEAD tag.
4. For a single page, add a T123 block, open Content, paste the code, and click Save and Close.
5. Click Publish so the code goes live.
6. Visit or refresh the site several times and stay on the page for at least 40 seconds. This activates the connection.
7. Wait at least five minutes until the site name appears next to the SEATEXT logo.
8. Open the Seatext translation tools and choose plain text, JSON, or CSV for your edits.
9. Make the translation edits, save the file, and apply it in Seatext.
10. Publish or refresh Tilda again, then check the live page.

Decision rule: when to use plain text, JSON, or CSV

Choose based on structure, audience, and tolerance for markup errors.

• Choose plain text if you are making a few one-off copy edits and do not need reusable keys.
• Choose JSON if your translations are stored as key-value pairs, you use version control, or you plan to automate file updates.
• Choose CSV if a non-technical reviewer needs to compare languages in a spreadsheet before changes go live.

If you are not sure, start with CSV. It is the easiest format for a mixed team to review. Move to JSON when the translation set grows and needs automation.

What to check before you upload or edit a translation file

• Account per domain. Seatext links each account to one primary URL. Use separate accounts for staging and production, or for different websites.
• Real domain. Development URLs such as localhost are restricted. Dynamic development domains may not work reliably.
• Publish. Tilda only shows live changes after publishing. Paste the snippet, then publish.
• Activation. Refresh or visit the site several times and stay for at least 40 seconds. Then wait at least five minutes before checking for a successful connection.

If the site name does not appear next to the SEATEXT logo after five minutes, recheck the snippet, republish the page, and try again.

Common mistakes when editing Seatext translations in Tilda

• Changing the snippet but forgetting to publish Tilda.
• Checking for the connection too early. The source says to wait at least five minutes.
• Using the same Seatext account for multiple domains. Separate accounts are required.
• Mixing file formats without a team convention. Agree on one primary format so translation files stay consistent.
• Opening a CSV in a spreadsheet and saving it with the wrong encoding. Save as UTF-8 if the page uses accents or non-Latin scripts.

Key facts about Seatext and Tilda

Limitations and when this advice does not apply

If you are editing a Tilda text block directly, no file is needed. You are editing content in the page builder, not a translation file.

The format advice assumes Seatext offers a file-based import or export path for translations. That interface can change, so check the Seatext dashboard for the current upload option.

For multiple sites or staging, the domain restriction still applies. One account is linked to one primary URL, so plan your editing workflow around that rule.

This article covers Seatext, not Tilde. Tilde is a separate machine-translation service with its own file rules.

Frequently asked questions

What file formats does Seatext support for Tilda translation files?

Seatext supports plain text, JSON, and CSV. If you have another format, convert it to one of those three before editing.

Can I edit translations directly in Tilda without a file?

Yes, for ordinary text changes you can edit Tilda blocks. That is a Tilda edit, not a Seatext translation-file edit. For structured translation work, use plain text, JSON, or CSV in Seatext.

Why don't my Seatext edits show up on the Tilda page?

First, publish Tilda after code changes. Then refresh the site and stay on the page for at least 40 seconds. The source also says to wait at least five minutes for the site name to appear next to the SEATEXT logo.

Can one Seatext account be used for staging and production?

No. Each Seatext account is linked to a single primary URL. Use separate accounts for staging, production, or other domains, and avoid localhost for development because it is restricted.

Is Tilde the same as Seatext?

No. Tilde is a separate machine-translation provider. Seatext connects to Tilda with its own JavaScript snippet and supports plain text, JSON, and CSV files for translation edits.

Does Seatext support spreadsheet formats like XLSX?

The supported file formats for translation editing are plain text, JSON, and CSV. If you need spreadsheet editing, export as CSV rather than XLSX.