Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Whiteboard is a Cloudflare-hosted meeting plugin. Each meeting has one board, and its content persists across sessions of that meeting.
- On the web, put the participant token in the plugin URL's #authToken= fragment and allow clipboard access before the iframe's first load. Mobile SDKs provide the WebView that hosts the plugin.
- Only a participant with a valid token for the meeting can open its board, but every participant with the board open can edit it; presets do not control Whiteboard editing.
- Board content is kept indefinitely and is not cleared when a session ends. There is currently no API to clear or delete it, and a removed participant's token remains usable until expiry.
- The documentation gives no plan fees, regional or account eligibility, or numeric board and capacity limits. Check applicable access terms and participant notices before relying on the plugin.
Start with the hosted meeting board
Cloudflare RealtimeKit Whiteboard is a collaborative plugin hosted and operated by Cloudflare. Register it through the plugins API you already use; you do not need to deploy or operate a separate whiteboard service. Participants can draw, write and diagram together, and see the cursors and RealtimeKit display names of others who have the board open.
Each meeting has one board. It remains the same when a new session of that meeting starts, so late joiners and reconnecting participants can continue with the current content.
Use one plugin ID across web and mobile
The web plugin URL follows this form: https://whiteboard-v2.plugins.realtime.cloudflare.com/#authToken=<auth_token>. Put the participant's current auth token after # in the URL fragment; do not put it in a ?authToken= query parameter. Browsers do not send the fragment to servers or include it in Referer headers, and the plugin removes the token from its address after loading.
Create the iframe before initializing the SDK and set allow="clipboard-read; clipboard-write" before its first src load, or the browser may block copy and paste. The guide's example also sets referrerPolicy="no-referrer". Pass the iframe as the plugin component and reuse that same element for the life of the meeting.
For Android, iOS and React Native, the RealtimeKit SDK creates the WebView that hosts the plugin; pass the plugin URL with the token fragment during registration. Use the same plugin id on every platform so activation syncs among participants who registered it. You do not need to register your app's origin.
Opening the board and editing it are separate permissions
The plugin verifies the participant token with RealtimeKit and opens the board for that token's meeting; you do not pass a separate meeting ID or participant name. Only a participant with a valid auth token for the meeting can open its board, and the token determines which board is used.
Every participant who has the board open can edit it; presets do not control Whiteboard editing. Plugin permissions control who can activate or deactivate the plugin. UI Kit participants can use the plugins panel, while a custom interface can call the activation or deactivation action; either action applies to everyone in the session.
The Whiteboard guide says that a participant's auth token remains valid until it expires even after the participant is removed from the meeting, so that person can still open the board until expiry. Do not treat removing a participant as an immediate end to this Whiteboard access; the Whiteboard documentation reviewed here does not describe a faster cutoff.
Board content is retained indefinitely, with no clear API
Cloudflare stores the meeting's board content on its infrastructure, including shapes, lines, freehand strokes and text added by participants. It is kept indefinitely and is not deleted when a session ends. There is currently no API to clear or delete a board.
Participants can enter personal or sensitive information. You are responsible for telling them that board content is stored and for meeting legal or regulatory obligations that apply to your use. Use of Whiteboard is subject to your agreement with Cloudflare, so decide whether this retention model fits the meeting before enabling the plugin.
Participant cursors and display names are shared only with people who have the board open; they are not stored with the board. This statement is limited to board storage and does not establish the retention period for other RealtimeKit data.
Supported content and capacity limits
Participants can draw shapes, arrows, lines, freehand strokes and text, and can export the board as an image. The plugin does not support images, frames, embedded web content or importing board files; participants see a message when they try to use these features.
The number of participants connected to a board is limited, and both the board and individual elements have size limits; the documentation gives no numeric values. When the participant limit is reached, new users cannot connect and see a Reconnect button. When the board or an element is too large, new changes are not saved and participants see a message.
For webinars or other large audiences, Cloudflare recommends letting a small group edit and sharing the board with everyone else through screen sharing. Plan around a collaborative meeting rather than a large broadcast.
Check account terms and data notices before rollout
The Cloudflare announcement is dated Nov 11, 2026, while the Whiteboard guide page displays Oct 26, 2026. Those page dates do not establish broad availability for any region, plan or account. The pages reviewed do not state fees, regional eligibility or account activation requirements, so confirm current access and applicable terms before depending on the plugin.
This guide is based on Cloudflare's announcement and documentation; no live account, plugin installation or meeting was tested. Before launch, consider checking plugin display, participant access and editing, cross-session content and the participant notice in an authorized test meeting. That is a pre-launch recommendation, not a test result.
Sources
Frequently Asked Questions
What should I do about Rejoin the meeting or Cannot verify your meeting?
Rejoin the meeting means the token is invalid, expired or for a different meeting; pass that participant’s current valid token in the plugin URL. Cannot verify your meeting means the plugin could not reach RealtimeKit to check the token, so select Try again. Neither message establishes a change in plan or regional eligibility.
Should I keep reconnecting after Too many attempts?
This limit applies after too many connection attempts from the same network in a short period. Cloudflare says to wait a minute, then select Try again. Repeated reconnects or switching proxies should not be treated as a way around that limit.
What should I check if the board cannot load or web paste does nothing?
For Cannot load the whiteboard, check the participant’s network connection, then retry. For failed copy or paste, check that the iframe had allow="clipboard-read; clipboard-write" before its first load. If the attribute was added afterward, reload the iframe.