Clear about
where it plays.

X Frame publishes Player Cards for compatible experiences. Websites with a verified player keep their own player. Other sites that permit embedding on both X and X Frame can use our compact player. When private browsing is enabled, other websites can run in a separate browser streamed into the player.

A working example.

Small Theft Crypto’s October 7 post exposes a live Player Card for its browser game. Its shared page declares a dedicated player, and that player specifically permits embedding by X. This is current evidence of the Player Card mechanism.

Why some sites open elsewhere.

Website owners decide where their pages may be embedded. A page that works inside X Frame can still block X, and a native player that allows X can block an extra X Frame wrapper. We inspect these permissions and use the existing player directly when appropriate.

We do not remove a website’s restrictions. Sign-in, wallet connections, fullscreen, browser controls, and game performance can also depend on the destination and browser.

A private browser for other websites.

The website opens as a normal page in its own temporary browser. Its original security headers remain in place. X Frame displays the browser’s pixels and forwards your clicks, scrolling, and typing. Each visitor starts with a separate profile, without existing logins or extension wallets. The original website remains available through the arrow in the player.

Some websites may decline hosted browsers or require features available only in your local browser. Browser sessions end after 20 minutes or when disconnected. If capacity is full, visitors wait for an available browser; creating frame links has no hourly quota.

Across devices.

X controls how a card appears and opens on each client. Desktop web, mobile web, iOS, and Android have not all been verified. Correct player metadata requests an interactive card; it does not guarantee the same experience on every device. A normal launch link remains available.

Already shared a link?

X can retain a previously fetched preview. An existing post may continue showing its earlier summary card after the website changes. Test with a fresh frame link; X controls when an older preview is refreshed.

Cards need public pages and images that X can fetch. Private deployments cannot provide public previews. For ordinary links, see X’s link-sharing guidance.