[rdsubhas]

How is the built-in website translation story in Firefox? To be honest, the only reason I'm forced to use Chrome is the way translate quite seamlessly works, both the detection (with mixed-language content in sites with English ads) and the actual translation.

I did try Bergamot but that was a year ago, and the experience was not as good as Chrome...

[zeumo]

Support for in-place website translations has been introduced in FF 118, initially for a handful of western languages, now 50 languages. There is also support for translating highlighted text and user text with about:translations.

It's fully local, which means the translation might not be as good as what Google can do, but it's good enough to use, and in my experience it's usually faster, as there is no network latency (except for the first translation between a language pair, which takes a little while to download the weights).

[nagisa]

There are a couple built-in ways you can translate, all of them fully local. First is the full page translation and another that allows you to translate a selection (from the context menu.) Fully local nature, of course, reduces the translation capabilities, but I found the quality to be good enough to very rarely need an external service.

[aboardRat4]

>How is the built-in website translation story in Firefox?

It's broken.

The button is there and is clickable, and there even is an animation near the address bar, but it doesn't actually do anything.

[OuterVale]

Really good. I use it frequently and haven't had any reason to switch to an external offering. It can translate the whole page or just a snippet that you highlight.