For players / ROBLOX
Roblox Quick Login: another device, QR codes and checks before approval
Sign in on your own second device without copying a password. Identify the approving account, handle an expired code and distinguish Quick Login from an email code or recovery.
Decide which device is asking to sign in #
Quick Login connects a new sign-in request to a device where your Roblox account is already open. Start by naming the two roles: the new device receives access; the signed-in device approves it. A phone is not automatically the approving device simply because it has a camera. Check that Roblox on that phone is already in the account you intend to use. The process is for access to your own account, not for receiving items, votes or rewards.
Prepare both devices together before opening a request. A useful private note is “My laptop asks; my phone approves; expected username is the one on my profile.” That is an illustrative checklist, not a real login performed by this website. If you cannot access either signed-in device, begin with account recovery instead. Repeatedly opening the Quick Login screen will not create an existing session or establish ownership of an account you cannot access.
Request a fresh code on the new device #
Open the official Roblox sign-in screen on the device you want to add. Where available, choose Log In with Another Device. The official instructions describe a one-time code with a five-minute lifetime. Keep that request visible while using your other device. A code copied from a video, message, screenshot or another player's screen is not a request you created. Do not use it to test whether the feature works.
For example, a learner opens a request, then spends several minutes looking for the approving phone. If the displayed code expires, the useful next action is a fresh request on the new device, followed by its corresponding confirmation. There is no benefit in trying variations of an expired code. Avoid keeping several pending screens open because that makes it harder to match the request you are approving to the device you actually want to add.
Open full-size image ↗Approve only the matching request #
On the device already signed into the intended account, open Account Settings and Quick Login. Read the displayed warning, enter the code from your own new device and review the request details. The final access approval is consequential: it authorizes another device to use the account. Stop if the device, account or request does not match what you just initiated. A claim that approval is needed to collect free Robux does not change its purpose.
Use a two-part check before confirming: “Is this my requested device?” and “Is this the correct approving account?” In a household with several profiles, these can have different answers. Ask the owner to operate their account rather than requesting their password or remote approval. Our diagrams show the relationship between screens, not a reproduction of a live Roblox security prompt. Follow the actual details Roblox displays, rather than expecting every device to show identical wording or positions.
If the QR route does not work #
When the sign-in screen offers QR login, use the code shown on your own new device. Roblox recommends an updated app and an already signed-in scanning device. A camera opening something does not prove the account login completed. Check the destination and the request before approving. If the camera cannot handle the QR flow, the official help also describes entering the six-character code as an alternative; use the option actually shown in your flow.
Do not scan a QR image sent by someone claiming to verify your inventory or restore a purchase. The image's appearance does not establish who receives access. If a scan leads somewhere unexpected, stop and return to your own request. Keep the devices near each other as the feature's help requires. Availability can differ, and a missing button alone is not proof of an account ban. Use another official sign-in method available to you rather than installing a supposed unlocker.
Confirm the account on the receiving device #
A successful approval should be followed by a successful sign-in on the new device. Check its Roblox username before playing, changing settings or purchasing anything. Familiar avatar clothing or a Display Name is a weaker check than the intended username. An approval animation on the old device and an open game on the new one are separate observations. If the new screen still asks for a code, record that stage instead of saying the entire process worked.
The diagnostic table separates an expired request, a QR problem and an unexpected account. Change one thing at a time, then inspect the receiving screen. An example result is “Created a fresh request; approved it on the intended phone; verified the expected profile on the laptop.” Another valid result is “No Quick Login option available; switched to an official recovery route.” Neither requires sharing a screenshot containing a current login code with other players or this website.
Open full-size image ↗Choose the next help without exposing codes #
Quick Login, an email one-time code, a passkey and an authenticator challenge are different routes. The location where you obtain the credential matters. This guide concerns approval from an existing account session. For a code expected in email, follow the separate email-code guide linked below; for lost access, use recovery. If access looks unfamiliar after an approval, review account sessions and the hacked-account help rather than approving additional requests in an attempt to reverse the first one.
For support, describe the device types, approximate time, chosen method and the exact stage that stopped. Remove passwords, active codes and private account details from attachments. A concise report might say “The new device showed a request, but the approving device reported expiration.” That gives a reproducible stage without transferring access. These instructions describe an official workflow and original teaching examples; they do not claim we signed into your account, tested every console or can guarantee recovery on every device.
| Situation | Action | Verification |
|---|---|---|
| New device | Request your own code | Keep its screen open |
| Existing session | Check your account | Match the request |
| Access approval | Read the details | Check the new profile |
| Request expired | Create a fresh own request | Do not vary the old code |
| Camera trouble | Available code-entry route | Match the same request |
| Unexpected profile | Stop new approvals | Review account sessions |
