Free public number
$0- Public messages are visible
- Used by multiple visitors
- No registration required
- Best for low-priority testing
Use a free virtual number or temp number to receive SMS online from Kwai and, where Kwai accepts public or virtual numbers, to sign up for a Kwai account without paying for the number. You can also compare paid one-time and private options when you need more control. This page currently displays 10 public message records from the available MyTempSMS snapshot. Public messages are visible to everyone; number availability, Kwai acceptance, verification, and delivery are not guaranteed. MyTempSMS is independent from Kwai.
Choose a country
Check priceChoose a country
Check price| Feature | Free public number | One-time verification | Private rental |
|---|---|---|---|
| Best for | Testing or low priority | Quick verification | Frequent or long-term use |
| Cost | $0 | Varies by country | Varies by country |
| Number type | Shared | Single use | Private |
| Message visibility | Public | Order-specific | Private |
| Reusability | Multiple visitors | Single use | During rental |
| Active duration | While available | Until verified or expired | Selected rental period |
| Delivery guarantee | Not guaranteed | Not guaranteed | Not guaranteed |
| Setup time | Instant | At checkout | At checkout |
Select one of the free public numbers displayed for this visit then stay on the same number's inbox. Continue only with your own Kwai / 快手 account action, and treat unrelated texts in the shared feed as someone else's traffic. Kwai’s account-recovery guidance says a user with an active bound mobile number can sign in with the phone number and a verification. A received text does not override Kwai / 快手's account rules.
Select one of the free public numbers displayed for this visit then stay on the same number's inbox. Continue only with your own Kwai / 快手 account action, and treat unrelated texts in the shared feed as someone else's traffic. Kwai documents verification-code delivery as part of phone-based access and tells users with missing codes to check the bound/current number, carrier state. Verify the message belongs to your request, not another visitor's.
The recovery guide emphasizes using the phone number actually bound to the account. It also notes that some regions may not support the carrier-code route, so availability can depend on. Messages displayed on a shared number page are publicly visible rather than private account communications. A received text does not override Kwai / 快手's account rules.
Kwai’s account-recovery guidance says a user with an active bound mobile number can sign in with the phone number and a verification code. Kwai documents verification-code delivery as part of phone-based access and tells users with missing codes to check the bound/current number, carrier state, filtering, device status. Different account stages can invoke different verification rules.
Kwai’s Account Protection can require an authentication code when a new device signs in and may require the user to link a phone first. Kwai supports third-party sign-in for accounts already linked to those providers, and Kwai Studio shows password and QR-based login choices in addition to phone plus. Follow the platform-specific path before trying another number.
If the bound number cannot be used, Kwai directs users toward a linked third-party account or its official recovery/support steps. Messages displayed on a shared number page are publicly visible rather than private account communications. For a permanent account, use private recovery credentials.
Verify the number format and make sure the code request came from the account flow you intended to use. Kwai documents verification-code delivery as part of phone-based access and tells users with missing codes to check the bound/current number, carrier state, filtering. If the issue persists, use the documented alternative or support channel.
When the phone field itself is rejected, the useful question is which account rule is failing rather than whether the inbox can receive texts. The recovery guide emphasizes using the phone number actually bound to the account. It also notes that some regions may not support the carrier-code route, so availability. Correct the account rule before retrying, then escalate through support if needed.
When the original phone or security factor is gone, avoid reconstructing the account around a shared inbox. If the bound number cannot be used, Kwai directs users toward a linked third-party account or its official recovery/support steps. Keep the existing account identity and restore access through the documented recovery path.
Select one of the free public numbers displayed for this visit then stay on the same number's inbox. Continue only with your own Kwai / 快手 account action, and treat unrelated texts in the shared feed as someone else's traffic. A received text does not override Kwai / 快手's account rules.
Kwai’s account-recovery guidance says a user with an active bound mobile number can sign in with the phone number and a verification code.
Kwai documents verification-code delivery as part of phone-based access and tells users with missing codes to check the bound/current number, carrier state, filtering, device status, and network conditions.
The recovery guide emphasizes using the phone number actually bound to the account. It also notes that some regions may not support the carrier-code route, so availability can depend on region and account state.
Kwai supports third-party sign-in for accounts already linked to those providers, and Kwai Studio shows password and QR-based login choices in addition to phone plus verification code.
Kwai’s Account Protection can require an authentication code when a new device signs in and may require the user to link a phone first. This is a device-security control separate from ordinary content use.
If the bound number cannot be used, Kwai directs users toward a linked third-party account or its official recovery/support steps. It also warns against repeatedly tapping the verification-code request.
Messages displayed on a shared number page are publicly visible rather than private account communications. Keep long-term recovery on private credentials you control.
Content review date: