# How Many Paywalls Show A Visible Close Or X Button?

Source: Lazyweb Research
Published: 2026-07-07
Sample size: n=2706
Tags: paywall, monetization, ux-patterns, mobile, design
HTML: https://www.lazyweb.com/research/how-many-paywalls-show-a-visible-close-x-button
Markdown: https://www.lazyweb.com/research/how-many-paywalls-show-a-visible-close-x-button.md

**Answer.** Of 2,706 mobile paywall screens with a vision description tracked by Lazyweb Research, 601 (22.2%) have a close or X control explicitly described [1]. In the mutually exclusive exit taxonomy, 517 screens across 120 companies are classified as visible-X paywalls [2]. The signal comes almost entirely from vision descriptions — only 7 CTA rows contain literal X/close text — so treat it as a lower bound [1].

> 22.2% of vision-described paywall screens (601 of 2,706) show a close or X control — Lazyweb Research, July 2026.

## The finding

A close/X control is described in 601 of the 2,706 paywall screens that have a vision description (22.2%) [1]. In the precedence-based taxonomy where visible X outranks text links, 517 screens (120 companies) land in the visible-X bucket [2]. That makes the X the most common visible exit pattern by a wide margin [2].

## The signal is visual, not textual

Only 7 of 4,406 CTA rows are literal 'X' or 'close' text [1]. Everything else about the X comes from vision descriptions of the screenshot. That has two consequences: the count is real but conservative (a missed description drops the screen), and you cannot reliably A/B an X by CTA text alone — it lives in the chrome, not the button list [1].

## How to apply it and caveats

If you add a visible X, you are matching the single most common soft pattern in the corpus [2]. Place it where users expect (top corner) so vision and users both register it. Caveat: 22.2% is a floor — vision descriptions omit some close controls, and OS back gestures are never captured [1]. All figures are what-shipped, not lift [1].

## The numbers

| Stat | Computed from |
| --- | --- |
| 601 of 2,706 vision-described screens (22.2%); 7 literal X/close CTA rows of 4,406 | vision_close_mentions: 601/2,706; dismiss_copy_leaderboard literal X/close = 7 |
| 517 visible-X screens across 120 companies | exit_type_taxonomy visible-X branch |

## Methodology

The 22.2% figure is over 2,706 screens with a vision description; the 517-screen taxonomy count is over 2,708 screens with visible-X precedence. Both rely on vision-description regex and are lower bounds. July 2026.

## Sources & citations

- [1] Lazyweb Research analysis of 2,706 vision-described paywall screens (mobile app corpus), July 2026. Close/X detected via vision-description regex; literal X CTA text is nearly absent, so the estimate is a lower bound.
- [2] Lazyweb Research analysis of 2,708 paywall screens (mobile app corpus, 120 companies with visible X), July 2026. Visible-X bucket in the mutually exclusive exit taxonomy.

## Related questions

- [How Do Apps Let Users Exit The Paywall — X Button, 'Maybe Later', Or Not At All?](https://www.lazyweb.com/research/how-do-apps-let-users-exit-the-paywall)
- [How Many Paywalls Use A 'Maybe Later' Text Link Instead Of An X?](https://www.lazyweb.com/research/how-many-paywalls-use-a-maybe-later-text-link)
- [What Percent Of Paywalls Have A Visible Dismiss Option?](https://www.lazyweb.com/research/what-percent-of-paywalls-have-a-visible-dismiss-option)