Frequently asked questions
Cloud phone questions, answered.
Plan capacity, check app workflows, and understand payment status before you begin. Third-party apps keep their own account and feature requirements.
Remote Android and plans
Remote Android and plans
What exactly is a CloudPhoneBase cloud phone?
It is a remote Android environment you access in a browser. Use it to keep a project’s apps, sign-ins, and web context together.
Is it the same as an emulator on my computer?
No. A CloudPhoneBase cloud phone runs remotely and opens through the browser, while an emulator runs on hardware you manage locally.
How many devices are included with each plan?
Essential covers one cloud phone, Plus up to three, and Workspace up to 25.
Does CloudPhoneBase offer a physical Android phone option?
Yes. CloudPhoneBase offers real Android phones hosted in the USA for $15 per month per phone. This is an additional service for projects that call for physical hardware.
When can I access my cloud phone?
Activation is handled manually. Confirm availability and the expected activation time with support before payment.
Apps and everyday use
Apps and everyday use
How do I check Android app compatibility?
Verify installation, sign-in, the exact action you need, and any browser handoff before relying on an app for important work.
Is Snapchat compatible?
Yes. Snapchat is compatible with CloudPhoneBase. App features and account requirements vary, so check the workflow your project needs.
Which Android apps can I use?
CloudPhoneBase supports a broad range of Android apps, including Snapchat. App features, account checks, and regional requirements can vary, so review the exact workflow for any essential app.
What should I do if an app step fails?
Identify the stage first: installation, sign-in, browser handoff, or a specific in-app feature. Recheck the current app requirements, then contact support with the device purpose, app name, and failing step.
Orders and payment
Orders and payment
How do I pay?
Checkout shows the crypto asset, network, amount, and configured fixed receiving address. Verify every field before sending. Card payment is not listed, and a different network or asset should not be substituted.
Why does checkout use a fixed address?
The configured receiving address is part of the crypto instructions for the service. Copy the address from checkout, verify it before sending, and never interpret an address shown elsewhere as a replacement for the order instructions.
When is a payment confirmed?
Payment is confirmed only after manual verification. A wallet submission, transaction identifier, or local success message does not by itself change the order status, and payment confirmation does not mean that device delivery has occurred.
What information helps with payment support?
Provide the order reference, selected plan, crypto asset and network, transaction identifier if available, and the status currently shown. Never send a password, private key, or seed phrase.
Need a specific answer?
Bring the app, order, or device context.
Use the help centre for guided steps, or send a message with the details that make your question identifiable.