Web app can't enter full screen? What to check

You click a web app's full-screen button, but the page stays the same size, shows an error, or only fills part of the browser window. The browser may support full screen while the app, the way it was opened, or the click itself prevents the request.

Use Browser Info to check which browser and browser features you have, then test the app in a clean tab. This helps separate a browser limitation from a problem with the app or the page hosting it.

Check the browser and the app

1. Open Browser Info in the same browser where the app has a problem. Note the browser version, engine, and supported features. This is a useful baseline, but it cannot confirm that a particular app is allowed to enter full screen.
2. Return to the web app and use its own full-screen button or menu item. If the app asks you to click again, do so. Browsers commonly require a direct user action before a page can enter full screen.
3. Notice what happens. Check whether the page expands, the browser shows a message, or nothing changes. If the app is inside another website, try opening it in a new tab and repeat the test.
4. Try the same app in an up-to-date browser you already have. Use the same account and page, and click the app's full-screen control rather than a browser shortcut.

Use the same display and window size for each attempt. If you change several things at once, it is harder to tell which one made a difference.

What the result means

The app enters full screen in another browser

The first browser, one of its settings, or an extension is likely involved. Compare the browser versions in Browser Info, update the browser, and test again with extensions disabled. If the app works in a private window, an extension or saved site data may be affecting it.

The page expands, but browser controls remain visible

This may be the browser window entering its own full-screen mode, rather than the web app taking over the display. Those are different actions. On Windows, F11 commonly hides or shows browser controls. On macOS, Ctrl + Cmd + F commonly changes the browser window's full-screen mode. Neither shortcut proves that the app's own full-screen request works.

The app works when opened in a new tab

The page that embeds the app may not allow full-screen requests. Web pages placed inside an embedded frame need permission from the page that contains them. If you manage the site, check the frame's full-screen permission. Otherwise, use the app's direct link or ask the site owner to fix the embedding.

Nothing happens in any browser

The app may not support full screen on that device, or it may be failing before it sends a request. Confirm that you are using the app's own control, that the page has finished loading, and that the page is secure. Full-screen features generally require a secure page, such as one using HTTPS, or a local development address.

Browser Info shows a relevant feature as unavailable

Browser Info reports browser details and supported features, but the report does not test the app's code, its embedding page, or every device restriction. An unavailable feature points toward a browser or platform limitation. If the report does not list a specific full-screen feature, that alone does not show that full screen is unsupported.

How to fix it

1. Click the app's control directly. Full-screen requests are commonly restricted unless they follow a click or tap. A request made automatically when a page loads, or after a long delay, may be rejected. Return to the app and click its control again.
2. Open the app outside an embedded page. Use an option such as open in new tab if the site provides one, or visit the app's direct address. If you maintain the embedding page, check that its frame is allowed to request full screen.
3. Reload the page and close other app windows. A failed or stale page can leave the control unresponsive. Save your work first, reload, and try again before changing browser settings.
4. Update the browser. Install the latest stable version available for your device, then restart it. Recheck the version in Browser Info and test the app again.
5. Test without extensions. Extensions that change page behavior can interfere with app controls. Try a private window if extensions are disabled there, or turn extensions off one at a time and reload the app.
6. Check the app's device support. Some web apps limit full-screen mode on phones, tablets, or particular browsers. If the app works on a computer but not a phone, the limitation may be intentional rather than a setting you can change.

Full screen is not usually controlled by a separate camera-style permission in Windows or macOS. You generally do not need to grant screen-recording access just to make a page fill the display. If the app is asking to share or record your screen, that is a different feature with its own browser prompt.

Why an app can be blocked even when the browser supports it

Browser support is only one part of the request. The browser can reject it if it was not triggered by a recent click or tap. An embedded frame may also need permission from the page around it. Some browsers and mobile operating systems impose extra limits, especially for content inside another app or a restricted browsing view.

That is why a supported-features report is a starting point, not a guarantee. If one app fails in every browser, report the device, browser version, and whether the app was embedded or open directly to its support team.