---
title: "Discussion on \"How to Build a Translator with Chrome’s Built-In AI\" | Hashnode"
description: "Discussion on \"How to Build a Translator with Chrome’s Built-In AI\". Most translation features work the same way. The user types text, your app sends it to a translation API, and the API sends a translation back. That works, but every request adds cost and latency, and"
url: "https://hashnode.com/posts/how-to-build-a-translator-with-chrome-s-built-in-ai/6afb9d63e1e477f325473f68"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How to Build a Translator with Chrome’s Built-In AI](https://freecodecamp.org/news/how-to-build-a-translator-with-chrome-s-built-in-ai?utm_source=hashnode&utm_medium=feed)

Most translation features work the same way. The user types text, your app sends it to a translation API, and the API sends a translation back. That works, but every request adds cost and latency, and

18h ago · 30 min read · freecodecamp.org  
Read the article

-   [#ai](https://hashnode.com/tag/ai)
-   [#api](https://hashnode.com/tag/api)
-   [#accessibility](https://hashnode.com/tag/accessibility)
-   [#translation](https://hashnode.com/tag/translation)

## Written by

[David Aniebo](https://hashnode.com/@davidaniebo)

@davidaniebo

  
[View profile](https://hashnode.com/@davidaniebo)

Driven by clarity, powered by code.

Software Engineer focused on building and maintaining reliable systems.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
