Web translation is not only about the target language. It also decides where text goes, who bills the request, and which settings follow you across devices. 77Fox keeps three sources explicit.
What it can do
Webpage Translation handles body text, tables, and dynamic pages, with full-page and selected-text workflows. Choose a plan cloud model, your own API key, or the local model. Translations appear beside the source DOM instead of replacing it, and stopping restores the page. See the 77Fox browser extension.
What it solves
AI power users move constantly between foreign-language docs, forums, and AIGC research. Cloud mode removes setup, BYOK gives provider and cost control, and local mode sends source text only to a loopback service on the current device. Sources never switch silently, so data and billing boundaries stay clear.
Who it is for
Vibecoders can read API docs, geeks can follow overseas communities, and freelancers can scan client material. Pick cloud for convenience, BYOK when you already manage a provider account, or local when on-device processing matters and preparing an approximately 2 GB model is acceptable.
How it works with the dashboard
Non-sensitive translation settings can sync between the extension and desktop. API keys never enter that mirror, and local model files stay device-local. The dashboard places translation status beside prompts, tasks, and extension management, so reading can lead directly to action.