locize documentation
Help Center
Blog
Sign in
locize.com
Search…
Introduction
Using locize
What's inside?
CDN (Content Delivery Network)
Tags
Translation Memory
Review workflow
History
Auto - Machine Translation
User management
The different views
Checks/Issues
Using locize as a translator
Integration
Getting started
Instrumenting your code
API
Webhook
CLI
I18n Formats
File Formats
Guides / Tips & Tricks
Find unused translations
How to search
Going to production
Keeping track of new translations
Working with translators
Migrating an i18next project
Migrating from ...
More
InContext Editor
Versioning
Namespaces
Caching
Backend Fallback
Latency Optimization – Tips for Optimal Performance
Notifications
2-factor authentication with Yubikey
2-factor authentication with TOTP
Convince Your Boss Letter
General questions
Powered By
GitBook
CDN (Content Delivery Network)
If not turned off, translations will automatically be published to our CDN.
There is no need to download translations or to redeploy your app for changes to take effect.
Under the hood, we are leveraging the power of
Amazon CloudFront
with edge locations all over the world.
There's also the possibility to define a custom
Cache-Control max-age
value per version, which can
optimize the latency
even more.
We suggest to create an additional
production
version and enable caching on it.
Do I have to use the locize CDN or can I host / bundle the translations directly?
I want to use our CDN, but would like to have a fallback that uses local / bundled translations?
Previous
What's inside?
Next
Tags
Last modified
2d ago
Copy link