Substack now translates your posts into 18 languages, by default

In June 2026 Substack shipped post translation to every user. By August it was on by default, and to turn it off you have to go looking through settings.

If you publish on Substack and have not touched that toggle, your posts are already being served to readers in other languages. That is a bigger change than the announcement made it sound.

What it actually does

Two directions, and they are not symmetrical:

• From English into 15 languages for longer-form posts
• From more than 100 languages into English

The full list of supported post languages is: Arabic, Catalan, Danish, Dutch, English, English (British), Finnish, French, German, Icelandic, Italian, Japanese, Norwegian, Polish, Portuguese (Brazilian), Portuguese (European), Spanish, Swedish and Turkish.

Readers see posts and Notes translated into whatever their device language is set to, on web and in the app. If you have published a custom translation for a language, readers get your version rather than the machine's.

Note English (British) sitting in that list as a separate entry from English. Substack is treating the two as distinct enough to warrant their own version — which is a fair judgement, and the subject of a whole separate problem for writers.

Why this is a real shift, not a feature announcement

Three things follow from it, and only the first is obvious.

Your addressable audience stopped being "people who read English." A newsletter in Lagos, Manila or São Paulo is now legible to a reader in Istanbul without either of them doing anything. Substack's own pitch — the post you publish in English finding readers in Istanbul, the newsletter you write in Japanese building an audience in Buenos Aires — is not marketing exaggeration. It is what the default now does.

The money follows, and Substack has the numbers. Nearly 100,000 publishers are earning on Substack globally, almost 30,000 of them outside the United States, with European creators alone earning more than $90 million a year. Substack also prices subscriptions in 13 currencies with local payment methods, and reported an 85% relative lift in paid conversion when local payment methods were offered.

Translation without local currency pricing would be a novelty. Together they are a distribution change.

You have lost some control over your own register. This is the part nobody is discussing. If you write with irony, idiom, wordplay or deliberately regional voice, a machine is now rendering that into Turkish for a reader you cannot see, and you did not approve the output. You cannot review it. You will never know how it read.

What it does not do

Be clear about the limits before you plan around it:

It does not translate your emails. The default email version goes out in the language you wrote. Translation is a reader-surface feature on web and app.

It is machine translation. Substack lets you write custom translations per language in the editor, and readers get those in preference to the automatic version. If a language matters to you commercially, write the version yourself or pay someone. Do not let the default speak for you in a market you care about.

It does not fix discovery. A Turkish reader still has to find you. Substack has added country leaderboards — currently France, Italy, the Netherlands, Spain and the UK — which is the discovery half of the same strategy, but it is early and narrow.

What I would actually do about it

Go and look at the setting. Publication Settings → Basics → Allow automatic translation and Additional post languages. Whatever you decide, decide it deliberately rather than by default.

Then decide honestly whether your writing survives translation. Reported journalism, analysis, how-to and argument travel well. Comic writing, heavy idiom, cultural in-jokes and anything carried by voice do not. If you write the second kind, the automatic version may be actively misrepresenting you, and turning it off is a defensible choice.

Write cleaner if you leave it on. Shorter sentences, fewer idioms, explicit rather than implied logic. This is the same discipline that makes writing better for non-native English readers generally, so it is not a sacrifice.

Pick one or two languages and do them properly. If your analytics show real readership in a market, write the custom translation for that language rather than letting the machine handle it. That is where the paid conversions are.

The wider point

Substack is not the first platform to make auto-translation the default, and it will not be the last. The direction of travel is that nearly everything that can be translated will be.

For writers this cuts both ways. Your reach goes up without any effort. Your control over how you sound goes down, in languages you cannot audit. Both of those are now true whether or not you opened the settings page.

The only real mistake is not knowing which one you chose.

Feature details from Substack's own product announcements and support documentation, checked 6 September 2026. Substack ships changes frequently — confirm the current language list in your own settings before planning around it.