Skip to content

Guides

Android 16 Ignores Portrait Lock on Tablets: What It Means for Website Apps

For apps targeting Android 16, a portrait lock no longer keeps your app in a phone-shaped box on tablets and foldables. Here is what Google changed, what a website app will show instead, and a short test plan.

Updated 11 min read

Android 16 ignores portrait orientation locks on tablets and other large screens for apps that target Android 16 (API level 36). On displays with a smallest width of 600dp or more, the app fills the whole window, whatever its manifest says about orientation or resizing. For a website app, that means users on those devices see your site at full tablet width, so your own responsive CSS decides whether it looks polished or stretched.

What did Android 16 change for large screens?

Google's Android 16 behavior changes page, last updated October 28, 2026, says that for apps targeting Android 16 (API level 36), orientation, resizability and aspect ratio restrictions no longer apply on displays with a smallest width of 600dp or more. Apps fill the entire display window regardless of aspect ratio or the user's preferred orientation, and pillarboxing (the empty bars beside a narrow app) is not used.

Smallest width

600dp+

where the restrictions are ignored

App must target

API 36

Android 16

Temporary opt-out

Gone at API 37

Android 17 removes it

Google lists the settings that stop having an effect on those screens. The manifest attributes screenOrientation, resizeableActivity, minAspectRatio and maxAspectRatio are ignored, and so are the runtime calls setRequestedOrientation() and getRequestedOrientation(). Portrait and landscape values, including the reverse and sensor variants, are ignored too. Checked November 14, 2026.

Which apps and screens are exempt?

  • Games, identified by the android:appCategory flag.
  • Users who explicitly opt in to the app's default behaviour in the device's aspect ratio settings.
  • Screens smaller than sw600dp (smallest width of 600dp).

Because screens below 600dp are exempt, the change is about tablets, large foldable displays and desktop-style windows. Whether a particular device crosses the 600dp line depends on its screen, so check the device you care about instead of assuming. The change applies in both full-screen and multi-window modes, according to the same Google page.

The rule only bites once an app targets API 36. If you are not sure what your app targets or why Google Play asks for it, our guide to Google Play's target API requirement explains how the level is chosen and when it rises.

What does this mean for a website inside an app?

The app can no longer stay in a narrow, phone-shaped column on a large screen, so the web view gets the full window width. Android's guide to supporting different screens in web apps says WebView converts CSS pixels to density-independent pixels, so a page looks the same size as on a medium-density screen. Put together, a 600dp-wide window is roughly a 600 CSS pixel viewport. That is an inference from Google's two pages, not a figure Google states, but it gives you a sensible number to test against.

The same guide says you usually set the viewport width to device-width and then use CSS media queries to adapt layouts to different screen sizes. It also notes that WebView does not use wide viewport mode by default. A page that relies on a fixed 980px desktop layout, or that only has one phone breakpoint, is the likeliest to look odd at tablet width.

Rotation matters as well. Google warns that allowing device rotation causes more activity re-creation, which can lose user state if it is not preserved. For a website, treat that as a prompt to test: rotate the tablet in the middle of a long form or a checkout and see whether the page keeps what the user typed.

There is a second rotation effect on Android 17 devices. Google says that when a configuration change such as rotation is not handled by the app itself, the keyboard's previous visibility is no longer restored. So someone typing in a form may rotate a tablet and find the keyboard gone, in addition to any lost field values. Our Android 17 guide for website apps sorts that change and the rest of Google's API 37 list by how likely each is to reach a site in a web view.

How to test your site at tablet size

  1. 1

    Check the viewport tag

    Your pages need width=device-width, initial-scale=1 in the viewport meta tag. Without it the layout can render at the wrong width.

  2. 2

    Resize in your browser

    Use your desktop browser's responsive mode at roughly 600, 800 and 1024 pixels wide, in portrait and landscape shapes. These are suggested checkpoints, with 600 chosen to match Android's threshold.

  3. 3

    Look for stretched content

    Long lines of text, full-width buttons and single-column forms across a wide screen are common problems. A maximum width on your main content column usually fixes them.

  4. 4

    Check fixed bars

    Sticky headers, bottom tab bars and cookie banners should still look sensible when they span a much wider window.

  5. 5

    Test on a real tablet

    If you can, install the app on a tablet or foldable, rotate it during a form, and try split-screen, since Google says resizability limits are ignored in multi-window mode as well.

A quick pass/fail table for your test session
CheckPass looks likeCommon fail
Text columnReadable line length with marginsText runs edge to edge across the tablet
NavigationMenu and tabs fit and stay usablePhone-sized hamburger menu floating on a wide header
FormsFields and buttons sized sensiblyGiant inputs, or values lost after rotation
Images and videoSharp and sized to the layoutBlurry upscaled images in wide containers
Fixed elementsStay aligned and out of the wayOverlap content or sit in odd corners

System bars can also overlap content at the top and bottom of the screen on recent Android versions, which is a separate problem with its own fix. We cover it in what to do when your website app content sits behind the status bar, and the broader mobile layout checklist is in how to optimize your website before turning it into an app.

What if I build the Android app myself?

Google describes a temporary opt-out. To exempt one activity, add the manifest property android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY with a value of true inside the activity element. To cover the whole app, place the same property inside the application element. Apps that use the opt-out go back to the earlier behaviour of being placed in compatibility mode.

Google marks this as temporary. Its Android 17 page, last updated October 28, 2026, says the opt-out is removed for apps that target API level 37, so it buys time, not a permanent exemption. You can preview the stricter behaviour by enabling the UNIVERSAL_RESIZABLE_BY_DEFAULT flag in the app compatibility framework. Google's own recommendation is to make the app adaptive so it works at any window size, which for a web view app means making the website itself responsive.

Frequently asked questions

Does Android 16 stop apps from locking to portrait on tablets?
For apps that target Android 16 (API level 36), yes. On displays with a smallest width of 600dp or more, Google says orientation, resizability and aspect ratio restrictions are ignored and the app fills the window. Games, user opt-ins and screens under 600dp are exempt.
Does this change affect phones?
Google says the restrictions still apply on screens smaller than sw600dp, so the change is aimed at large screens such as tablets. Whether a specific phone or foldable crosses the 600dp line depends on its display, so test on the device you care about.
Can I opt out of the Android 16 large-screen behaviour?
Only while the app targets API 36. Google documents the android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY manifest property, which can be set per activity or for the whole app, but Android 17 removes the opt-out for apps targeting API level 37.
Will my website look different inside the app on a tablet?
It can. The web view gets the full window, so your CSS breakpoints decide the layout. Pages with only a phone layout may look stretched, so test at widths around 600 pixels and above.
Do games get an exception?
Yes. Google's Android 16 page lists games, identified by the android:appCategory flag, among the exceptions to the orientation, resizability and aspect ratio changes.
Why does the keyboard disappear when I rotate my tablet inside the app?
On Android 17 devices, Google says the keyboard's previous visibility is not restored after a configuration change such as rotation that the app does not handle itself. Test form typing and rotation on a real tablet, and ask your app builder how rotation is handled.