CartVisualCreate account

Why Did Adobe Express Translate Use a Font Outside Our Restricted Brand Library?

Adobe documents an exception: translated pages may need fonts beyond the restricted brand or library for accurate rendering. Review the resulting script coverage and approved fallback instead of treating the font change alone as proof that every brand control failed.

Published · By CartVisual editorial team

Separate a documented exception from a broken lock

A brand team restricts an Adobe Express poster to its approved typefaces. After a collaborator translates the poster, the new page uses another font. The team’s first reaction is to rebuild the template or remove every collaborator’s editing access. First check whether the changed page came from Translate. Adobe explicitly documents that translated pages can require fonts outside the restricted brand or library.

The same official explanation notes a separate case: a font already present in the published template can remain accessible in its remixes even when it is absent from the brand or library. Record whether the font appeared through translation or was inherited from the source template. Those are different paths to investigate; neither observation establishes that all brand restrictions have been disabled.

Trace the actual fallback trigger

The documented shared-template brand restrictions apply to Teams and Enterprise. Adobe separately explains that Translate keeps original fonts where possible but switches when the source font lacks characters needed by the target language. Default fonts may be used for Chinese, Japanese and Korean. This automatic fallback is different from a brand owner deliberately approving a typography system.

Record the source-template font and exact approved source string. Identify the required target-language characters, then inspect the resulting font and fully rendered translated text. If the original lacks those characters, the documented automatic fallback is a relevant explanation. If the unlisted font was already in the published source, investigate inheritance instead. If neither path explains it, retain the actual page and configuration for further investigation rather than declaring every brand control broken. Wait for the text to finish rendering before comparing the final layout; a preferred brand font does not guarantee future automatic selection.

Record what must stay fixed

For a localized product poster, separate the exact product name, approved translated meaning, brand identity and readable character shapes. A Latin-only brand font may be unsuitable for the target script. That does not authorize a translator to change the offer, omit a condition or draw approximate substitute characters. The task is to agree on a usable fallback and approve the resulting layout.

Observed changeQuestion to resolveAppropriate evidence
New font on a translated pageWas the documented Translate exception involved?Source template, translated page and selected typeface
Unlisted font available in a remixWas it present when the template was published?Original published-template font inventory
Boxes or missing characters remainDoes the selected font actually support the required script?Exact approved string at final size
Readable translation changes the offerWas the meaning altered?Fluent copy review, separate from font selection

Resolve one localized page before rebuilding the template

Consider a fictional lamp poster translated into Japanese. The reviewer keeps the approved product name and offer in a separate text record. A language-capable fallback is proposed for the translated headline. Compare the exact characters, punctuation, line breaks and condition text in the actual page and export. Inspect the merchandise image independently; a typography repair is not a reason to alter the lamp’s proportions.

If the fallback is readable and acceptable to the brand owner, document its intended language scope. If it is unsuitable, obtain an approved alternative and verify the resulting file. Do not promise that adding a font to a library alone proves future translated pages will use it. This example has not been executed in an Adobe account.

Approve the translation and its governance separately

The translated-copy layout guide explains preserving meaning when text expands. The template versus campaign approval guide explains why approving the reusable template does not approve every output. Here the additional decision is how a documented font-enforcement exception enters that review.

Close the investigation with a recorded source-template version, translation language, chosen font, approved string and final export. Revisit the organization’s template configuration only after distinguishing the documented exception from an actual configuration discrepancy. A brand restriction is useful governance, not evidence that the translated poster has already passed human review.

Sources

Scope and evidence

Prepared by CartVisual with AI assistance and checked against the listed sources. These are documented third-party workflows and illustrative editorial exercises. No account operation, software test, order, payment, production print, generation or publishing was performed. Check current account options and the actual delivered asset.

Related decisions

Explore the product poster maker workflow