MoPub Format Unification

The MoPub SDK v5.8 release simplifies the ad unit creation process for publishers by automating the information that the SDK collects. At the same time, the release increases flexibility in creative sizes, enabling more DSPs to bid on an impression.

Release Highlights

Creating ad units is faster and simpler.

We have simplified the process of creating an ad unit in the Publisher UI. Instead of creating a separate ad unit for every size, screen orientation, and device type within an ad format, you will now simply select from the available ad formats. We have simplified the selections to five choices: banner, medium rectangle, fullscreen, native, and rewarded ad. The SDK will collect the remaining data automatically.

The SDK now collects the safe area in real time.

The SDK can collect the available ad real estate for any ad format. For banner ads, publishers can specify the safe area of your ad via the iOS, Android, and Unity SDK integration APIs; and for fullscreen ads, the SDK will dynamically collect the safe area based on the device.

MoPub Publisher UI provides additional advanced features to default your unified banners to either 320x50 or 728x90 if your app is on an SDK lower than v5.8.0 or does not specify a size in the SDK on v5.8.0 or above. This feature is a safe area fallback; if no size is available, this size toggle in the UI will enable us to set the fallback default size to the ad unit’s current settting.

Additional creative sizes are now supported.

You are no longer limited to the few standard ad size dimensions offered in the Publisher UI. Our existing formats now support multiple additional creative sizes. The SDK collects the available dimensions for an ad display and our ad server then automatically identifies eligible creative sizes. In addition to the existing sizes, the below new sizes are added to the formats.

  • New sizes for Banners: 300x50, 468x60, 970x90, 970x250
  • New sizes for Medium Rectangles: 336x280
  • New sizes for Fullscreen: 320x568, 300x600, 360x640, 300x1050, 568x320, 640x360

Extended supply for non-native display opportunities.

Enabling additional creative sizes for ad formats positions us to meet demand from DSPs and advertisers to serve more creative sizes than we have in the past. Bid requests now contain all acceptable creative sizes for the ad unit, and DSPs can respond with any one of the sizes listed, including the newly added sizes.

End-user experience improves.

Video ads will now display in the correct device orientation as picked up by the SDK, so the user can enjoy a better fullscreen experience, without the need to reorient their devices.

Affected Components and Processes

Publisher UI

The process of creating a new ad unit is now streamlined.

  • You no longer need to provide ad size specifications.
  • You no longer need to create a separate ad unit for each size.
  • You no longer need to specify device type (phone or tablet).
  • You no longer need to specify device orientation for fullscreen ads.


The SDK automatically collects device orientation and sends it to the ad server.

  • For banner ads, the publisher passes to the SDK the maximum real estate for banner ads via newly added API calls

  • For fullscreen ads, the SDK collects the available real estate from the device, taking into account not only device size, but physical device specifics that vary across models, such as notches and other physical features. The SDK then sends these dimensions to the ad server, which optimizes the available Marketplace demand.

After the ad server identifies eligible creative sizes, it sends them to DSPs inside a format array as part of the bid request. The MoPub platform optimizes the available Marketplace demand and creative displays based on the available ad format sizes.

Bid Requests and Responses with DSPs

Bid requests will now contain a format array containing a subset of acceptable widths and heights, when applicable, enabling DSPs to respond with a creative for any of the dimensions listed. Bid responses from participating DSPs will include the dimensions of the creative the DSP is proposing.

MoPub encourages DSPs to adopt the new format array into their systems. Doing so increases the inventory available to DSPs and the number of impressions their creatives can fill. We are working with our demand partners as an increasing number of them integrate this new format.

Take Advantage of Our New Unified Formats

To take advantage of the unified formats going forward:

  1. If you are using an earlier version of the MoPub SDK than 5.8, upgrade your MoPub SDK to version 5.8.

  2. For banner ads, pass banner sizes in your API calls to the MoPub SDK:

    • For Android: Instead of calling moPubView.loadAd(); as before, you will now pass in the size by calling moPubView.loadAd(MoPubAdSize);.

    • For iOS: This has not changed. Continue to pass in the banner size as before:

      • If you know the size of the banner you’d like to request, call loadAdWithMaxAdSize:custom_CGSize.

      • If you don’t know or have the size of the banner you’d like to request, and you’d like to use a constant, call loadAdWithMaxAdSize: and pass in one of the recognized MoPub ad size constants as listed here.

      • If you would like to use the frame as the maximum ad size, pass in the kMPPresetMaxAdSizeMatchFrame constant.

    • For Unity: Instead of calling MoPub.CreateBanner(adUnitId, position) as before, you will now pass in the size by calling MoPub.RequestBanner(bannerAdUnit, position, maxAdSize);.

  3. Upgrade mediation adapters if you are partnering with AppLovin or Facebook. The adapter versions listed here are required for compatibility with MoPub SDK version 5.8.

    • Refer to adapter upgrade instructions for AppLovin.

      • Android: implementation ‘com.mopub.mediation:applovin:’ (changelog)
      • iOS: pod ‘MoPub-Applovin-Adapters’,’ (changelog)
    • Refer to adapter upgrade instructions for Facebook.

      • Android: implementation ‘com.mopub.mediation:facebookaudiencenetwork:’ (changelog)
      • iOS: pod ‘MoPub-FacebookAudienceNetwork-Adapters’, ‘’ (changelog)

New Ad Units

Going forward, you will always create new ad units as unified ad units in the Publisher UI.

  1. In the Apps tab’s App details page, click New ad unit. The New ad unit screen has changed to require less information:

    Format Unification New Ad Unit

  2. As discussed in the Publisher UI section of this document, there are various fields you are no longer required to fill in. For the remaining fields, follow the instructions in our documentation to create a new ad unit.

Convert Legacy Ad Units

Convert legacy ad units to unified ad units in the Publisher UI:

  1. In the Apps tab’s Ad unit details page, click Edit ad unit. The new Edit ad unit page now has a convert option.

    Format Unification Convert Ad Unit

  2. Click Convert to unified ad format. You can see back at the App details page, which lists all of your app’s ad units, that legacy ad units have a different appearance from unified ad units:

    Format Unification Compare Ad Units

  3. Repeat steps 1 and 2 for every legacy ad unit.

    Note: Direct Serve ad units cannot be converted to a unified format.


What are the advantages of using unified ad units?

Unified ad units are simpler and faster to create and maintain, and allow you to extend your existing supply by supporting additional ad sizes for DSPs.

Do mediated networks support flexible width and height?

This varies from network to network. Facebook Audience Network supports flexible width; Google AdMob supports both flexible width and height. Other networks only serve standard-sized creatives, which will be centered in the MoPub views if the views are larger than the creatives.

Going forward, for any new ad unit, you will not need to create multiples to account for size or orientation differences.

What will happen if a publisher is auto-migrated but is on an SDK < v5.8?

  • Banners: Ad units created before September 16, 2019 will serve 320x50 creatives only.
  • MRECT: Ad units created before September 16, 2019 will serve 300x250 creatives only.
  • Leaderboard: Ad units created before September 16, 2019 will serve 728x90 creatives only.
  • Fullscreen: Ad units will serve creative based on the device height and width.

Should publishers be archiving old “Tablet” ad units post migration? When should they?

No, they should leave as is until all the impressions on the the old “Tablet” ad units have diminished.

To what will the safe area fallback default once the ad unit is unified?

The safe area fallback size will be assigned based on the ad unit’s legacy size. This only applies to 320x50 and 728x90 ad units created pre-unification.

Do all supported network adapters support format unification?

Yes, all supported network adapters are compatible with v5.8+.

Last updated August 28, 2021

TWITTER, MOPUB, and the Bird logo are trademarks of Twitter, Inc. or its affiliates. All third party logos and trademarks included are the property of their respective owners.

© 2021 MoPub (a division of Twitter, Inc.)