The images in this article were generated with artificial intelligence. How we publish
Google has started to allow some users in the United States to modify the previous part to @ gmail.com of your account: that is, to change the main user name or create an alias that becomes the address associated with the account. This is a relevant development because, so far, Google allowed to add aliases and alternative addresses, but not replace the @ gmail.com address that serves as the main identifier to log in and receive mail.
The company announced it on its own blog and on the help pages, where they explain that from the account configuration you can choose a new user name, as long as it is available and not in use on another account. The process is done from the Google account section; after choosing the new name and confirming the action, the old address is no longer the main and the new one appears in services such as Gmail, Drive or Photos. You can check the official ad on Google's blog Here. and explanation in the account support Here..

It is important to understand that this is not just a temporary alias: in making the change, the direction you used is no longer the main address of the account. Google, however, has pointed out that it will not release that name for others to claim; the former identifier will remain linked to your account, with which no one else will be able to register it. This decision reduces the risk that other people will start receiving emails addressed to your old identity, but does not eliminate other practical consequences that need to be anticipated.
In terms of use, Google promises that the new address will be reflected almost immediately in the company's services ecosystem. Still, there are nuances: third party applications, services or websites that have registered you with your previous address may have been left with that value as an identifier. In some cases the modification will not automatically update that information and you will have to notify the change or log in with the new mail if the supplier supports it. It is therefore recommended to review the most critical integrations before proceeding.
From a security and recovery perspective, changing the main address requires a review of the methods associated with the account: recovery mail, phone number, and sessions initiated on other devices. If you depend on the old address to receive codes or to restore access to certain services, it is appropriate to add the new address as a confidence contact and to verify that two-step verification and recovery mechanisms continue to function properly.
The functionality was first detected at the end of last year and, according to Google, it now begins its deployment in the United States. This means that not all users will see it immediately; if you do not find the option in your configuration, it probably has not yet reached your account or region. Google has not required a public calendar of global availability, so those outside the United States will have to wait for a gradual expansion of deployment.
For those who are thinking of taking advantage of it, there are also practical or aesthetic reasons for doing so: updating a past name of fashion, correcting typographic errors, unifying professional and personal identities, or simply choosing a more memorable direction. But this benefit should be assessed against the operational cost of communicating the change to contacts, updating profiles in external services and checking that the rules for filtering or forwarding to mail customers are not broken after the change.
Another precaution: although Google indicates that it will keep the old name linked to your account, there are still scenarios where the public visibility of the mail (for example, in contact lists or in systems that store old copies) can cause confusion. Make a small communication campaign - warn your most used circle, update your email signature and, if appropriate, publish the change in your professional profiles - reduce friction.

In the technical field, the most obvious limitation is the need for the new name to be no longer in use. This maintains the integrity of the system but also means that those with short or arbitrary directions for years may not find an identical alternative. In addition, accounts managed by organizations (Google Workspace) or initially created with addresses that do not end up at @ gmail.com may remain subject to different standards; if your account is under a business or educational domain, check your administrator's policy before trying to change.
If you want to check if the option is available to you, enter myaccount.google.com, go to the personal information section and look for the option to change the email associated with the account. Before pressing any button, make sure you make a mental list of the services that use that address as an identifier and prepare a plan to update them: that will save you unpleasant surprises after the change.
In short, the ability to change the previous part to @ gmail.com opens a useful door for those who want to redefine their digital identity but it's not a purely cosmetic decision. As with any changes that affect the main identifier of an account, it deserves a serene assessment of risks and benefits, and some practical preparation. For official information and details of the steps and conditions, always check the Google pages linked to the ad and the technical support.
Related
More news on the same subject.

Four Plex2Shell CVE allows remote execution and mining and proxy backdoor deployment
In recent days, an increase in attacks has been confirmed that take advantage of a chain of failures in Plex Media Server - nicknamed "Plex2Shell" by researchers - to run code r...

GhostAction Expands Attack: phishing to steal credentials and persistence in VS Code
A group behind the GhostAction campaign - already known for infiltrating GitHub Actions workflows into open source projects - has expanded its arsenal: in addition to installing...

ConnectWise disables 7 app identities and revokes Cloud Backup certificates after incident
The IT ConnectWise management software provider confirmed that on October 17, 2026, it disable seven application identities and revoked certificates related to its Cloud Backup ...

Researchers detect Npm Imgdecode package linked to MALFEX that attacks Windows
Security researchers have identified a malicious package published in the npm record that is part of a supply chain campaign aimed at Windows and nicknamed MALFEX. The package, ...

OpenBSD 7.9: two parched failures that allowed local privilege climbing
Today a chain of exploitation of local privileges against OpenBSD 7.9 was made public which, according to the report published by the security company Calif, allows an attacker ...

OpenAI reveals unaligned IA incidents; a GPT-5.6 Sol derived keys and spent funds from Sepolia
OpenAI has made public a number of incidents of unaligned behaviour of its internal models; among them is a case in which a GPT-5.6 family research model Sol derived private key...

Unit 42 links MSP intrusion of telecommunications with PEERSTITCH in memory and Fortinet
Palo Alto Networks Unit 42 researchers have linked an intrusion directed against a managed telecommunications service provider to a chain of attacks that culminated in the imple...