TranslatePress makes an important distinction in its automatic-translation documentation: installing the plugin does not itself provide access to a translation provider’s API. Google and DeepL connections have their own account and key requirements, separate from the WordPress files.
The developer also describes storing translated strings in the database so that the same untranslated text does not have to be sent repeatedly for translation. That changes how a site owner should think about the cost: a growing catalogue and a frequently rewritten catalogue can create different workloads, even when they have a similar number of pages.
A daily limit is an operational decision
The automatic-translation settings include a character limit and an option to stop indexing crawlers from triggering translations. Those controls deserve attention before enabling a new language across a large site. A quiet trial on a few pages is more informative than discovering the cost after the whole catalogue becomes eligible.
Review the actual customer journey, too. A translated product description does not prove that the basket, account screen and order email use the intended language. Follow one purchase with a test account and check each stage as a visitor would encounter it.
Business and the free core use different version numbers
The downloads below are TranslatePress Business 1.8.8 and TranslatePress Multilingual free core 3.3.8, as named in GPLHub’s current listing. The two version numbers describe different components; 1.8.8 is not being presented as the version of the free core.
TranslatePress documents its additional modules in the add-ons reference. This page supplies the Business package and its free core, not a separate collection of every historical add-on. Cross-version compatibility still needs a staging check.
Readers searching for TranslatePress nulled should keep software files, vendor support and machine-translation credit separate. No hosted translation allowance or vendor account is included here.
