ClearRules
Back to ClearRules

Temporary 2FA code generator

Already have your authenticator setup key? Use it here to calculate a code. This does not turn on 2FA or recover a lost key.

Your setup key can generate future login codes. Treat it like a password. Do not send it to support, put it in a link, or use this tool on a shared device.

For everyday access, use a dedicated authenticator app. Never enter a key someone sent you or asked you to test.

Use the setup key Instagram offers to copy when you enable 2FA with an authentication app. This is not your password, an SMS or email code, the current login code, or a backup code.

Before completing setup, make sure a trusted authenticator is configured for this account. Securely save any backup codes the service offers. Do not rely on this page alone: it does not save the setup key.

Where do I get the setup key?

The service shows this key when you set up two-factor authentication with an authentication app. The key lets an authenticator generate new login codes. ClearRules cannot find or recover it for you.

In Instagram or Facebook

  1. Open the official app or website yourself and go to your account settings.
  2. Look for Accounts Center → Password and security → Two-factor authentication. Select the account you need, if asked.
  3. Choose Authentication app. On Instagram’s key setup screen, tap Copy key. On Facebook, look for a text key or manual-setup option near the QR code, if offered.

You may see Meta Account instead of Accounts Center. Menu names and available options vary by app version and account.

What does the key look like?

A long string of Latin letters A–Z and digits 2–7, sometimes grouped with spaces. Its length varies. Plain keys can include lowercase letters and spaces here; digits 0, 1, 8 and 9 are not accepted. Copy the full key exactly rather than inventing or shortening one.

How do I get the login code?

Paste the key here, read the safety warning and confirm that you understand the risk, then select Generate code. Enter the resulting code only in the official service where you started signing in or setting up 2FA. Setup is complete only when that service accepts the code and confirms it; this generator alone does not enable 2FA.

2FA is already on, but I don’t have the key

The old setup key may no longer be visible. Keep your working authenticator and recovery methods. Use the code in your existing authenticator, a backup code on the service’s sign-in screen, or the service’s official recovery process. Do not turn off 2FA just to use this generator.

Only a QR code? Look for a text-key option in the service’s setup screen. This page cannot scan or upload QR images. It also accepts supported setup text beginning with otpauth://totp/.

For daily sign-ins, use a trusted authenticator app. Never send your setup key to another person or paste it into a message, support chat or URL.

Official setup help: Instagram · Facebook

Key settings

Keep the settings supplied by your service. A pasted otpauth URI supplies its own settings; unsupported settings are rejected.

Technical limit: Base32 keys decoding to 16–128 bytes. A shorter legacy key needs a compatible authenticator. Keep any original trailing = characters; do not add padding yourself.

No key loaded

Refreshes in — seconds

Uses this device’s clock. The service decides how long to accept a code.

Clears after 5 minutes without interaction, or after 1 minute in the background. Returning to this page after navigating away starts empty. If the browser pauses this page, expired data is cleared when the page resumes.

Code not accepted?

Check that the key and settings belong to the right account. Turn on automatic date and time in your device settings, then wait for a fresh code. Repeated attempts can trigger a service limit.

No setup key? See access-recovery options

Read about two-factor protection

How this works

TOTP calculation follows RFC 6238 using your browser’s Web Crypto. Codes can still be stolen by phishing. We cannot verify that a key belongs to your account, or that your clock is correct.

This tool does not send your key to a server or save it in application storage. It uses it temporarily in this page. Your browser, extensions, device and clipboard can still expose it. Closing the page cannot guarantee secure erasure.

RFC 6238