Comet is Perplexity’s web browser for iPhone and Android, with an assistant for questions about what you are reading. A free version is available, but that does not mean every paid Perplexity feature is included. Start with a public webpage and a simple question before connecting accounts or asking it to act for you.
Official instructions checked November 11, 2026, for U.S. readers. This guide covers the Comet browser, not the separate Perplexity app. It does not report a hands-on speed, accuracy or security test.

Install the browser, not a similarly named app
Use Perplexity’s official Comet page as your starting point. It lists iOS and Android alongside the desktop versions and says a free version includes Comet. You do not need to begin by purchasing the most expensive Perplexity subscription.
On iPhone, the U.S. Comet App Store listing identifies Perplexity AI, Inc. as the developer and lists iOS 18 or later. The download is free with in-app purchases. Check the current compatibility and purchase screen rather than assuming that “free” includes unlimited AI use or that an upgrade prompt is mandatory.
For Android, Perplexity’s Android quick-start guide directs you to the Play Store, then Google-account or email sign-in. It currently specifies Android 12 or above. Its onboarding suggests making Comet the default browser; leave that decision until you have checked that the sites you use work as expected.
Try one page question before automating anything
A useful first task is reading assistance, not placing an order. Use this check with a public article or product page that contains no private account details:
- Open the page in Comet and bring up its assistant.
- Ask a narrow question, such as “List this page’s return deadline and any return shipping charge.”
- Ask where on the page each answer came from, then read the original wording yourself.
- If it answers about the wrong page, identify the intended tab explicitly and try a simpler question before trusting a longer task.
The Android guide describes asking the assistant to summarize the current page. It also describes using the keyboard microphone from the search bar to dictate a request. Perplexity’s iOS feature announcement describes built-in voice mode and questions across open tabs. Those are platform-specific instructions, not a promise that every phone has identical buttons or actions.
For shopping research, request a comparison or a draft list first. Check the retailer, model, delivery charge and final total yourself. An answer about a return policy is not the same as completing a return, and a cart suggestion is not proof that you bought something.
Continue on another device with Sync
Perplexity’s Sync Between Devices instructions separate account sign-in from the encrypted sync chain. In Settings → Sync, create a chain or join one using the passphrase from an existing device. The guide describes a four-word passphrase and warns that you need it to restore access after signing out.
Review the data types shown in your version instead of enabling everything by habit. The guide lists separate controls for items such as bookmarks, history, passwords and tabs; turning one off stops new updates while keeping local data. For another device’s open pages, look for Menu → Tabs on other devices. Do not treat a password-manager sign-in as proof that browser sync is configured.
Sync is not screen mirroring or remote control of your phone. If you meant to operate an iPhone from a Mac, see our separate iPhone Mirroring setup and connection guide. That solves a different problem from carrying browser pages between devices.
Check what the assistant can send and remember
“Stored locally” does not mean an AI page summary runs entirely on your phone. The newer Comet Assistant privacy and data-use guide says required context can be sent to Perplexity when you request a summary, selected-text extraction or information from another tab. It says relevant page, history or tab context may remain for up to 30 days for Library and query-history features.
That is more specific than the Android quick-start FAQ’s broad claim that all personal browsing data stays on the device. Treat the assistant’s task context, ordinary local browser storage and encrypted device sync as separate things. Before asking about a banking, work or health page, consider whether you want its contents included in an AI request at all.
The assistant guide lists controls under Settings → Privacy and security → Comet Assistant to disable it or block it on particular websites. It also describes first-run agent choices: allow this time, always allow, or do not allow. Prefer a one-time decision while you are learning what an action does; do not approve ongoing access just to dismiss a prompt.
If a request stops or the answer looks wrong
Check whether an ordinary webpage loads before troubleshooting an AI task. If both fail, compare your WiFi and mobile connection. If browsing works but the assistant fails, check the selected page, sign-in state and any on-screen permission or usage message. Keep sensitive details out of screenshots you send for support.
The Android quick-start guide says automated web tasks need the app to stay open and do not support background work. Do not start a task, switch away and assume it finished. Check the actual destination page or confirmation. Before repeating a request that could send a message, add an item or change something, find out whether the first attempt already did it.
Keep your usual browser available until you have tried your important sites. If Comet helps you read a public page but you are uncomfortable giving it broader access, that is a reasonable place to stop. You can use reading assistance without turning every online task over to an agent.