Locize offers two different Content Delivery Network (CDN) infrastructures to serve your translation files. You can choose the one that best fits your project's security, caching, and feature requirements.
The Standard CDN is the new default for all newly created projects. It is powered by BunnyCDN and provides a high-performance, cost-effective solution for most public-facing applications.
Cache-Control max-age.Since the default cache is 1 hour, you might see old translations during active development. You can bypass the cache using the following methods:
1. Using Query Parameters
Append ?cache=no to your fetch URL to force a fresh download:
https://api.lite.locize.app/{{projectId}}/{{version}}/{{lng}}/{{ns}}?cache=no
2. Using i18next-locize-backend
If you are using the official backend plugin, set the reloadInterval or noCache option:
import i18next from "i18next";
import Locize from "i18next-locize-backend";
i18next.use(Locize).init({
backend: {
projectId: "[PROJECTID]",
cdnType: "standard",
noCache: true // <-- set strictly for development to bypass cache
},
fallbackLng: 'en',
supportedLngs: ['en', 'de']
});
// Alternative configuration:
// If 'debug: true' is set in i18next, it will also bypass the cache automatically
// even if noCache is not explicitly set.
/*
i18next.use(Locize).init({
debug: true,
backend: {
projectId: "[PROJECTID]",
cdnType: "standard"
},
// ... other options
});
*/
The Pro CDN is the robust infrastructure that locize has used since the beginning. It is based on Amazon CloudFront and is designed for projects requiring advanced control, privacy, and safety nets.
Cache-Control max-age per version to optimize for latency or freshness according to your specific needs.
You can switch your project between Standard and Pro at any time in your project settings.

Depending on your integration you may need to change the cdnType option in your tools (CLI, i18next-locize-backend, locizify, locizer, etc.) or change the API endpoint.