Skip to content
Use cases

Review foreign-language work documents with translation

When a document exposes readable text in the browser, keep the original beside the translation and verify terms, numbers, and conditions as you review it.

Compare the supplier’s instructions with the source

This example uses an English web document. Try the three display modes, then use bilingual view when checking a measurement, deadline, or list of exceptions.

supplier.example/handbook/receiving

SUPPLIER HANDBOOK · RECEIVING

Receiving inspection and storage

Inspección de recepción y almacenamiento

Store unopened sensor kits between 10 °C and 25 °C. Check the lot number and the seal before moving the kits to storage.

Almacene los kits de sensores sin abrir entre 10 °C y 25 °C. Compruebe el número de lote y el precinto antes de llevar los kits al almacén.

If the seal is broken, set the kit aside and contact the supplier within two business days. Include the lot number and a photo of the package.

Si el precinto está roto, aparte el kit y póngase en contacto con el proveedor en un plazo de dos días hábiles. Incluya el número de lote y una foto del paquete.

Verify the details that change what you do

Compared with pasting text into a standalone translator such as DeepL, in-page translation keeps each instruction next to its original section and surrounding conditions.

Keep conditions next to the instruction
Check the original for units, exceptions, and deadlines before sending instructions to another team. Keep the source link next to any excerpt you share.
Use the terms your team already knows
Give the AI engine a glossary of product names, abbreviations, and approved translations. This helps keep terms consistent across pages of the same manual.
Check the document format first
Open the browser-readable HTML version, such as a supplier portal, online manual, or wiki. Use the site’s accessible text version when the source is a scan or browser-restricted file viewer.

Use your own API key on the Free plan

Choose My API Key in the extension to translate with a connected provider. Newey does not charge for this translation path, including on the Free plan.

  1. Open the Newey extension’s webpage translation panel. Under Translation engine, choose My API Key and select Connect a key.

  2. Choose a provider, enter its API key, and load or select a model that your account can use.

  3. Save and return to webpage translation. Choose the saved connection and check a short paragraph before translating a long document.

The provider applies its own usage limits and billing. Translation can cost nothing within an eligible provider’s free quota. Check the provider account for actual charges.

Examples of supported API connections

  • OpenAIGPT
  • AnthropicClaude
  • GoogleGemini

Check how the document opens

Documents you can read in a browser

For a help center, internal wiki, or HTML manual, turn on the extension and show both languages where the page text is accessible.

Attachments and scans

This workflow does not upload a file and produce a translated copy in the original format. Try the extension only when the browser can expose readable page text.

Review an overseas supplier’s instructions

Read the translation first
Locate the delivery checklist, revised process, and point of contact.
Compare against the original
Verify whether the deadline uses business days, which time zone applies, and which exceptions are listed.
Share findings with the team
Include your questions and the original passage or page link so colleagues can verify the details.

Before opening an internal document

  • Check which translation engine your organization allows for confidential material. Choose the built-in browser engine if the text needs to stay on your device.
  • For contracts, quotes, and policy documents, verify amounts, dates, and exceptions against the source and have the right person review them.

Frequently asked questions

  • This page covers webpage translation in the browser extension. It does not upload files, recreate document formatting, or export translated documents.
  • It depends on whether the extension can access the page and the browser exposes its text. Pages the extension identifies as sensitive use the on-device translation path.
  • Use a web document whose text is accessible to the extension, such as an HTML manual, supplier portal, or internal wiki.
  • Use bilingual display and compare quantities, units, exceptions, and business-day language. Include the source link with any excerpt you share.
  • Register the preferred wording in a glossary, select it with the AI translation engine, and translate the page again.
  • For a web document, select My API Key and a supported provider. Check the document’s policy for sending its text to that provider.
  • Webpage translation needs readable text. Check whether there is an accessible web-text version of the same document.
  • This workflow displays translations inside the browser. Share a reviewed excerpt and link back to the source when you pass it to your team.