PatternGuard is a free online tool that lets you draw and analyze unlock patterns for Android phones. No download needed — test different combinations and see in real time how secure each design is before using it on your device.
The analyzer combines length, starting point, direction changes, crossings, distance between points and whether the pattern is one of the most common ones into a score from 0 to 100. It is a heuristic estimate based on how people tend to choose patterns, not a guarantee of security. Starting in a corner lowers the score a lot: that is a project rule based on studies of where people start, with no data of our own, and edges and the center score the same for lack of data.
The pattern lock was introduced by Google with Android 1.0 in 2008. The concept emerged as a visual alternative to the numeric PIN: instead of memorizing a sequence of digits, users trace a shape across a grid of points, leveraging the brain's visuomotor memory.
Over time, pattern locks spread beyond phones: they now appear on Samsung and LG Smart TVs, Wear OS smartwatches, Android tablets, and some banking apps that offer a second level of in-app security.
A widely cited 2013 study by Uellenbeck, Dürmuth, Wolf and Holz — "Quantifying the Security of Graphical Passwords: The Case of Android Unlock Patterns" — analyzed real-world pattern choices and found that users pick patterns non-uniformly: they favor the upper-left corner as a starting point and short straight lines. The researchers estimated a partial guessing entropy of 9.10 bits for guessing 20% of the patterns, which is less than three random digits, meaning most real patterns are far easier to guess than the raw combination count suggests.
Compared to an alphanumeric password, a pattern loses on raw combination space: an 8-character password mixing upper case, lower case and digits exceeds a trillion possible combinations, far more than the 389,112 available on a 3×3 grid. In everyday use, though, that theoretical edge matters less than resistance to shoulder surfing: a pattern is traced as one visible gesture, while an attacker has to catch every individual keystroke to memorize an alphanumeric password — which in practice makes it much harder to copy with a single glance.
If you're locked out right now, don't panic — what happens next depends on what was set up on the device before you got locked out, not on anything you can fix in the moment. The three paths below cover the situations people run into most.
On many Android versions, after five failed pattern attempts a "Forgot pattern?" link appears, letting you sign in with the Google account linked to the device to unlock it — this needs the phone to have working internet access. Samsung devices linked to a Samsung account can instead be unlocked remotely through Find My Mobile, and any device with Find My Device enabled can be locked or erased remotely from google.com/android/find. None of these are guaranteed: some manufacturers and newer Android versions restrict or remove the account-based bypass for security reasons, so results vary by device and Android version.
When no bypass is available, a factory reset (usually done from the hardware recovery menu — power + volume buttons — if you can't get past the lock screen) is the last option. It erases the phone completely and only restores from whatever cloud backup existed before the lock; see the backup warning below before you rely on this.
If you can still unlock the phone and just want to stop using a pattern, go to Settings → Security (or Lock screen, depending on the manufacturer) → Screen lock, enter your current pattern to confirm, then choose "None," "Swipe," or another method like PIN or password.
Android uses the unlock pattern as part of the encryption for your phone's backup. This has an important consequence many users are unaware of: if you forget your pattern, Google cannot help you recover your encrypted backup.
Unlike your Google account password — which you can reset by email — the pattern is a local key stored on the device. Google holds the encrypted backup on its servers but does not have the key to decrypt it. If you lose the pattern, that backup is gone forever.
Recommendations: store your pattern in a password manager, enable a backup PIN in your device's security settings, or consider using a password instead of a pattern if you rely on encrypted backups.
If you've already forgotten your pattern and are locked out, your options depend on what was set up beforehand. If a Google account is linked, some Android versions offer a "Forgot pattern?" option that lets you unlock using that account's credentials after several failed attempts — but this doesn't work on every device or Android version, and some manufacturers disable it. If that option doesn't appear, a factory reset is usually the only way back in, which wipes the phone's contents.
It's worth distinguishing the local backup (a copy that lives only on the device's storage, encrypted with the pattern) from Google's cloud backup (which syncs contacts, apps and settings, but not all encrypted content). Losing the pattern mainly affects the local encrypted backup and any data tied to that key — not necessarily everything you'd already uploaded to the cloud before losing access.
On a 3×3 grid there are 389,112 valid patterns considering the intermediate point rule (if a line passes through an unselected point, that point is automatically added to the sequence). Without that restriction, the number exceeds 985,000 combinations. The more points, the more patterns: there are 1,624 patterns of 4 points, 26,016 of 6 and 140,704 of 9.
It depends on the pattern. Published studies show that people don't choose patterns at random: in a study with 800 participants, about 44% of the patterns started at the top-left corner. A long pattern with crossings that doesn't start at a corner is considerably harder to guess, but the space is still small: even chosen at random, a 9-point pattern (140,704 possible) has fewer combinations than a 6-digit PIN (1,000,000). PatternGuard helps you estimate how typical your pattern is with an indicative score, not a guarantee.
Grid size dramatically changes the space of possible combinations. A 3×3 grid has 9 points and 389,112 valid patterns; a 4×4 has 16 points and about 4.35 trillion; a 5×5 has 25 and on the order of 10²³ (estimated). In practice, though, people keep choosing predictable patterns, so more points on the grid don't guarantee a pattern that is harder to guess. On 4×4 and 5×5 the score uses a 9-point grid as its reference, just like 3×3: a pattern of 9 or more points with good traits can reach Very strong, and a short, straight one scores low on any grid.
Entropy measures the uncertainty of a pattern in bits. If the pattern were chosen at random among the valid ones with the same number of points, it would be log₂ of that count: on 3×3, about 17.1 bits with 8 or 9 points. PatternGuard shows that pattern space (counted with Android's rules, not with permutations of the 9 points) so you can compare sizes. But people don't choose at random: a 2013 study estimated just 9.10 bits to guess 20% of patterns, less than three random digits. That is why the score is not the entropy: it also looks at the starting point, direction changes, crossings and common patterns.
It depends on the device's setup. If a Google account is linked, some Android versions offer the option to unlock using those credentials after several failed attempts. If that's not available, a factory reset is usually the only way out, which wipes the phone and can only be recovered from a previous cloud backup.
In terms of possible combinations, a long alphanumeric password is the most secure, followed by a PIN and then a pattern. In everyday use, though, the real difference comes down to how each one is chosen: a long pattern with well-placed crossings can be more secure than a short, predictable PIN like "1234" or "0000". What matters isn't the method itself but avoiding the most common designs within each category.