Change the interface language
Use the language selector in the site or workspace navigation. It changes supported interface labels and public product pages. It does not translate an existing project's authored wording, replace its images or consume image credits simply because you changed the menu language.
These documentation articles are currently published in English. A language choice in the surrounding navigation does not imply that every editorial guide has a translated edition.
Choose the language for new work
Check the output-language control when creating a new AI plan. Describe the audience and any terminology that should be kept as supplied. New editable template content can use the selected document language; names, figures, brand assets and existing artwork are different kinds of content and need their own review.
When adding a new editable block to an existing project, the seed wording follows the document language. The same project should not switch its content language just because another collaborator uses a different interface.
Translate an existing project deliberately
Choose the target language
Use the explicit project-translation control, rather than the interface selector. Confirm which document you are translating.
Review the proposed work
Keep names, numbers and other protected details in your brief. Approve the plan when the target language and scope are correct.
Review the translated result
Check terminology, dates, contact details and every page's layout. Longer translations may need a different text size or more space.
Text inside artwork needs a different workflow
Changing editable text does not translate words already drawn into an image. Image editions may contain English artwork even when the interface is set to another language. Translating that artwork needs a separately approved image-editing or regeneration plan, with the image cost shown before approval.
For important professional, legal or application wording, have an appropriate reader review the final translation. Language support and automated layout checks are useful tools; they are not a claim that every phrase has been individually proofread by a native speaker.