When you're designing an ad in the Thunder editor, you may notice a discrepancy between how the text appears in the editor version and how it appears in the compiled preview. This is common when working with custom font files. 

Read below for some best practices to help keep discrepancies to a minimum

EDITOR VIEW

COMPILED PREVIEW

Consider the text bounding box as cage, or restraint for your text. You do not want this to escape out of the bounding box or move around during the compilation process.

During the compilation process, extra space in the bounding box can contribute to visual discrepancies between editor view and the compiled preview. 

BOUNDING BOXES

Once you have y our text asset placed on the stage, utilize the "min height" tool in the properties panel to immediately condense all extra space above and below your text asset.

Before

After

Note: Try to leave some horizontal space with your bounding box. If the box is too tight around the text horizontally, this might cause unwanted line breaks during compilation. 

Example

BOUNDING BOXES

For center aligned text, like in a CTA button, it is recommended to leave space on either side of the text.

COORDINATES

Stage your text assets on the stage at whole pixel coordinates. This helps the translation between the editor preview and the compiled preview. 

Recommended

Not Recommended

SCALING UP 

Scaling text above 1 can result in blurriness. Use "auto" text sizing, or change the font size manually if text needs to be at a specific line height.

Not Recommended

Did this answer your question?