Skip to main content
All CollectionsUsing NEXD Campaign ManagerAdvanced creation
Design for high or low aspect ratio mobile fullscreen sizes
Design for high or low aspect ratio mobile fullscreen sizes

What to know about different screen aspect ratios?

Updated over 3 years ago

As you probably have noticed, the mobile phone market has moved towards bigger screens – more than 55% of the global mobile phone market is on high aspect ratio screens.

Comparison between high and low aspect ratio devices:

What does this affect?

You should only worry about the different screen sizes when you use mobile fullscreen ads. These ads are overlaid or cover the content of the website or app.

What to notice while designing fullscreen ads?

As a rule of thumb, the creative design or positioning of the assets should be done so that:

  1. the background covers full height (using assets in size up to 640 x 1280 px). This ensures that there are no black or white areas outside the ad.

  2. important content is within the “safe area” (in the center with a maximum height of 854 px). This ensures that essential info appears even on smaller screens.

Designers use "safe areas" to ensure that your ads look great on all screens. You should also use them when creating fullscreen ads:

What to notice while placing assets?

Our Scale and Crop tool will help you position the asset within the limits. By default, the "safe area" is shown on the ad. You can also position assets without them or see the ad with browser bars:

If you are using our regular layouts, you don't have to worry when you place a CTA button or logo asset out of the "safe area" neither. It'll appear by default in the right place depending on the size of the screen visible area and will not disappear if the device is not a high aspect ratio one.

What to notice while previewing fullscreen ads?

You can also see how it is shown on high or low aspect ratio devices and with/without browser bars

  • When designing the creative above the quick preview:


  • On preview site:



Did this answer your question?