{"id":136,"date":"2026-11-13T07:47:15","date_gmt":"2026-11-13T07:47:15","guid":{"rendered":"https:\/\/www.strongrandompassword.com\/blog\/how-to-change-your-gmail-password\/"},"modified":"2026-11-13T07:47:15","modified_gmt":"2026-11-13T07:47:15","slug":"how-to-change-your-gmail-password","status":"publish","type":"post","link":"https:\/\/www.strongrandompassword.com\/blog\/how-to-change-your-gmail-password\/","title":{"rendered":"How to Change Your Gmail Password (and What to Check Afterwards)"},"content":{"rendered":"<p><strong>TL;DR:<\/strong> To change your Gmail password, go to <strong>myaccount.google.com \u2192 Security \u2192 How you sign in \u2192 Password<\/strong>, confirm your current password, then set the new one. Speed matters more than method: a compromised account is usually taken over within hours, and changing the password is only half the job \u2014 you also need to <strong>sign out all other sessions<\/strong> and check the recovery options, or the attacker keeps access.<\/p>\n<h2>The actual steps<\/h2>\n<p>Three routes get you to the same screen, and the direct URL is the one least likely to be a phishing page.<\/p>\n<p>Open <strong>myaccount.google.com<\/strong> directly by typing it, sign in, then Security \u2192 &#8220;How you sign in to Google&#8221; \u2192 Password. You will be asked for your current password before setting a new one.<\/p>\n<p>Two alternative routes: the Google app&#8217;s account menu, or the &#8220;Forgot password&#8221; flow if you cannot sign in at all. The latter is a different procedure and is covered further down.<\/p>\n<p>After the change, Google offers to sign out other devices. Accept that option. It is the single most important follow-up step and it is easy to skip because it appears as a secondary prompt.<\/p>\n<h2>What a password change does and does not fix<\/h2>\n<p>Changing the password invalidates existing sessions only if you explicitly sign them out. There is a real window where an attacker&#8217;s session survives the change, especially on mobile devices where the app may stay signed in.<\/p>\n<p>Three things to do immediately after:<\/p>\n<ul>\n<li><strong>Sign out of all other sessions<\/strong> at myaccount.google.com \u2192 Security \u2192 Your devices \u2192 Manage all devices<\/li>\n<li><strong>Review recovery options<\/strong> \u2014 an attacker who added a recovery phone or email keeps a route back in even after a password change<\/li>\n<li><strong>Check forwarding and filters<\/strong> in Gmail settings, because a common takeover technique is to forward copies of mail silently<\/li>\n<\/ul>\n<p>Those three checks take a few minutes and matter more than the password complexity. Most account takeovers that recur do so through a recovery option or a filter, not through the password being guessed again.<\/p>\n<p>Also revoke third-party app access under Security \u2192 Data &amp; privacy \u2192 Third-party apps. An old app authorisation survives a password change and can retain broad access.<\/p>\n<h2>Choosing a new password<\/h2>\n<p>The practical requirements, in order of impact.<\/p>\n<p><strong>Length beats complexity.<\/strong> A 16-character passphrase of ordinary words is stronger than an 8-character mix of symbols, and it is easier to type. Current guidance favours long passphrases over forced special characters.<\/p>\n<p><strong>Never reuse.<\/strong> The single largest risk is not a weak password on one site, it is a strong password reused across sites where one breach exposes the others. Credential-stuffing attacks exist precisely because reuse is common.<\/p>\n<p><strong>Do not derive it from the old one.<\/strong> Adding a digit or a year to a leaked password produces something attackers try first in their scripts.<\/p>\n<p><strong>Store it in a password manager, not your memory.<\/strong> A manager removes the pressure to keep passwords memorable, which is what forces reuse in the first place.<\/p>\n<p>If you need a random one, <a href=\"https:\/\/www.strongrandompassword.com\/\">a strong password generator<\/a> produces something with no pattern, which is the property that matters \u2014 memorable-looking patterns are exactly what cracking tools are optimised to try.<\/p>\n<h2>If you cannot sign in<\/h2>\n<p>The recovery flow is different from a password change and is worth understanding before you need it.<\/p>\n<p>Enter your email on the sign-in page and choose &#8220;Forgot password&#8221;. Google then walks through verification using recovery methods you registered: a phone number for a code, a recovery email, or a prompt on a device already signed in.<\/p>\n<p>Three failure modes are common:<\/p>\n<p><strong>The recovery phone is an old number.<\/strong> If you cannot receive the code, you fall back to account recovery, which asks questions about your usage and can take several days to resolve.<\/p>\n<p><strong>A device prompt appears on a device you no longer have.<\/strong> Waiting for a newer device to become available is often faster than pushing recovery questions.<\/p>\n<p><strong>The account is a Workspace account.<\/strong> If your email is on a company domain, the administrator controls the password reset and you cannot recover it yourself. Contact them rather than persisting with the consumer flow.<\/p>\n<p>This is why updating recovery options is worth doing now rather than during an incident. A password change is easy; account recovery is slow and uncertain.<\/p>\n<h2>Two-factor authentication<\/h2>\n<p>A password alone is increasingly insufficient, and the reason is structural: passwords leak through breaches you have no control over, so no amount of care protects you from a third party&#8217;s security failure.<\/p>\n<p>Three options, in order of strength:<\/p>\n<p><strong>Passkeys or security keys<\/strong> are phishing-resistant because they are bound to the real site&#8217;s domain. This is the strongest option and increasingly the default recommendation.<\/p>\n<p><strong>Authenticator app codes<\/strong> are strong against remote attacks, though a determined phishing page can relay a code in real time.<\/p>\n<p><strong>SMS codes<\/strong> are better than nothing and weaker than both, because SIM swapping and interception are real attack methods.<\/p>\n<p>Enabling any two-factor method is worth more than perfecting the password, and enabling passkeys is worth more than the other two combined.<\/p>\n<h2>After a suspected compromise<\/h2>\n<p>If the password change comes after noticing something wrong, the order of operations matters.<\/p>\n<p>Change the password first, sign out all sessions second, then audit. Checking settings before securing the account gives the attacker time to re-add access while you investigate.<\/p>\n<p>Then work through the audit: recovery options, forwarding rules, filters, third-party apps, sent mail for messages you did not write, and the account&#8217;s recent security activity page. Google&#8217;s security checkup consolidates most of this, and it is faster than checking each setting individually.<\/p>\n<p>Finally, change the password on any other account that used the same one. If the original password was reused, those accounts are exposed regardless of what happens to Gmail.<\/p>\n<h2>The short version<\/h2>\n<p>myaccount.google.com \u2192 Security \u2192 Password. Then sign out all sessions, verify recovery options, and check for forwarding rules \u2014 the password change alone is not enough. Use a long unique passphrase from a manager, and turn on passkeys or an authenticator app rather than SMS.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>TL;DR: To change your Gmail password, go to myaccount.google.com \u2192 Security \u2192 How you sign in \u2192 Password, confirm your current password, then set the new one. Speed matters more than method: a compromised account is usually taken over within hours, and changing the password is only half the job \u2014 you also need to &#8230; <a title=\"How to Change Your Gmail Password (and What to Check Afterwards)\" class=\"read-more\" href=\"https:\/\/www.strongrandompassword.com\/blog\/how-to-change-your-gmail-password\/\" aria-label=\"Read more about How to Change Your Gmail Password (and What to Check Afterwards)\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":36,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-136","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-security-practices"],"_links":{"self":[{"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/posts\/136","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/comments?post=136"}],"version-history":[{"count":0,"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/posts\/136\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/media\/36"}],"wp:attachment":[{"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/media?parent=136"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/categories?post=136"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.strongrandompassword.com\/blog\/wp-json\/wp\/v2\/tags?post=136"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}