Google’s 15GB Gmail promise now has a phone number test

Google has confirmed that it is testing a new storage policy for some new accounts in select regions, cutting the default free allowance to 5GB unless users add a phone number. The change is not yet a universal public policy, and Google has not announced a global rollback of the long-running 15GB free tier. But the test still matters. It changes the meaning of “free” storage from a blanket account benefit into a conditional offer tied to identity, account recovery, and abuse prevention. Android Authority reported Google’s confirmation on May 15, 2026, after users and tech sites noticed new-account prompts offering 5GB by default and 15GB after phone-number verification.

The reported change is smaller than a global rollback but larger than a UI test

The first point to keep straight is the scope. This is not a confirmed global end to 15GB for every Google Account. Google told Android Authority that it is testing a new storage policy for new accounts created in select regions and framed the test as a way to keep storage service quality high while encouraging users to improve account security and data recovery. That wording matters because it avoids declaring a permanent rule, but it also confirms the screenshots were not merely fake, misread, or caused by a local bug.

The observed flow is simple. A new account sees a message saying it includes 5GB of storage. The user is then offered a way to unlock 15GB at no cost by adding a phone number. The prompt, as reported by 9to5Google, says Google will use the phone number to make sure storage is added only once per person. That is not the same as asking users to buy Google One. It is a gate based on verification rather than payment, though the practical pressure is still real for people who do not want to attach a phone number.

The test sits inside a subtle wording change on Google’s own pages. Google’s help page now says each Google Account includes “up to 15 GB of storage” shared across Gmail, Google Drive, and Google Photos. Google One’s plan page uses the same “up to 15 GB” language. That phrase gives Google more room than the older promise many users remember, where 15GB sounded automatic.

The change is also easy to overstate. Existing personal Google Accounts have not been publicly moved down from 15GB because of this test. Android Authority’s own testing found an older alternative Gmail account without a phone number still showing 15GB. The reported prompt is about new-account onboarding, and even there it appears limited by region or account-creation path.

Still, the test is not trivial. Gmail is not a small app feature sitting at the edge of Google’s business. A Google Account is the entry point for email, cloud files, photo backup, Android, YouTube, Play, Docs, Calendar, and account recovery. A storage rule at signup can shape how people understand the entire Google ecosystem from the first minute of use. If the first screen says 5GB unless a phone number is added, the free account is no longer a clean 15GB promise in practice.

The most accurate description is this: Google is testing a conditional free-storage model for some new accounts, where 5GB is the default and 15GB remains available at no charge after phone-number verification. That sentence is narrower than “Google cut Gmail storage to 5GB,” but it captures the strategic shift better.

The reason the news traveled quickly is that Gmail’s storage history has always been part of its identity. Gmail launched with a storage pitch that felt unusually generous, then Google unified free storage across Gmail, Drive, and Photos in 2013. For more than a decade, the baseline answer to “How much free Google storage do I get?” was 15GB. A 5GB signup screen breaks that muscle memory, even if the full amount is still one verification step away.

Google is not the first cloud company to use identity signals, phone verification, quotas, anti-abuse controls, or tiered onboarding. What stands out is that storage is now being used as the reward. Instead of saying, “add a phone number for security,” Google can say, “add a phone number to unlock the storage users already thought they were getting.” That is a stronger prompt than a generic security reminder.

For users, the difference between 5GB and 15GB is not cosmetic. Gmail attachments, Google Photos uploads, Drive files, WhatsApp backups on Android, and files created or edited in Docs, Sheets, Slides, Forms, Recorder, and Vids can all count toward the shared quota under current Google storage rules. Google says going over quota can affect file uploads, photo backups, Gmail sending and receiving, and collaborative editing.

That means a 5GB starting point changes the runway for a new account. A user who relies on Gmail only may last a long time. A user who turns on photo backup, receives large attachments, uses Drive for school files, or carries Android WhatsApp backups could reach 5GB quickly. The new default, where tested, makes the account feel more fragile unless the user accepts phone-number verification.

The timing is also telling. Google is spending heavily on AI infrastructure and cloud capacity. Alphabet said in its Q1 2026 earnings call that capital expenditure was $35.7 billion in the quarter, with the overwhelming majority going to technical infrastructure supporting AI opportunities. Google Cloud revenue rose sharply in Q1 2026. Those facts do not prove Gmail’s storage test is caused by AI costs, and Google did not say that. They do show that storage, compute, and identity controls are being managed in a company under intense infrastructure pressure.

The deeper story is not “Google suddenly became stingy.” It is that the economics of free storage have changed, and the abuse profile of free accounts has changed with them. Free storage is no longer just a consumer perk. It is an infrastructure obligation attached to billions of identities, many of them dormant, duplicated, automated, fraudulent, or barely used. A 15GB automatic grant to every new account is generous for normal users but expensive and exploitable at scale.

Google’s test appears to answer that problem with a familiar trade: more quota for more identity confidence. It may be rational from an infrastructure and anti-abuse standpoint. It may still feel intrusive to users who view a phone number as sensitive personal data. Both reactions can be true.

Gmail’s storage promise has always been part of its market power

Gmail’s original appeal was not only search, threading, or the clean interface. It was storage. When Gmail arrived in 2004, the 1GB allowance was startling compared with the tiny inboxes common at the time. The Associated Press, writing on Gmail’s twentieth anniversary, described the 1GB launch offer as so large that many people thought the service was an April Fools’ joke.

That history matters because Gmail trained users not to think about deleting email. The product’s culture was built around search instead of manual filing, and abundant storage made that possible. The old email habit was to clean the inbox because the box was small. Gmail’s habit was to keep everything and search later. Storage was not a background spec. It was the behavioral engine of the product.

Google later widened the storage story beyond email. In 2013, the company unified storage across Drive, Gmail, and Google+ Photos. Instead of separate allowances, users received 15GB of unified free storage to use across the services. Google’s own Gmail blog said the change replaced 10GB for Gmail and 5GB for Drive and Google+ Photos with a shared 15GB pool.

That 2013 move did two things at once. It made storage simpler for consumers, and it made Google Account storage a platform layer. Drive could grow because unused Gmail storage was no longer trapped in email. Photos could ride on the same quota. Gmail became part of a broader personal cloud bundle rather than a separate inbox with its own allowance.

A 15GB free tier also gave Google a visible comparison advantage. Apple’s iCloud still starts with 5GB of free storage. Microsoft’s free OneDrive offer gives 5GB of cloud storage, while Microsoft separates that from mailbox storage in its consumer plans. Dropbox Basic starts at 2GB. Proton Drive starts lower but lets free users unlock more Drive storage through setup steps. In that field, Google’s 15GB has long looked generous.

The 5GB test narrows that visible gap. A new Google account without phone verification starts closer to Apple and Microsoft than to Google’s old image. The full 15GB can still be free, but the default becomes more conditional. The marketing advantage shifts from “Google gives more” to “Google gives more if you verify.”

That is a different relationship with the user. The old promise said storage came with the account. The test says the larger allowance comes with a stronger identity signal. The product benefit is now attached to a compliance action at signup.

The emotional reaction is predictable because users rarely separate storage from trust. A quota is not only a number. It tells people whether a provider is asking them to relax or asking them to monitor themselves. Fifteen gigabytes says: use Gmail, try Drive, turn on Photos, and see how far it gets you. Five gigabytes says: manage carefully from day one, or verify, or pay later.

Google’s official pages still position the free storage pool as shared across core services. That shared nature creates the user experience. A person does not usually think, “I am using 1.4GB of Gmail, 2.1GB of Drive, 800MB of WhatsApp backup, and 700MB of Photos.” They think, “Google says I am almost full.” A smaller starting pool turns small product decisions into account-level pressure.

This is why the test should not be judged only by whether 5GB is enough for email. Gmail is no longer only email. The quota crosses services, and Google has kept extending the list of items that count. After June 1, 2021, new Google Photos uploads in Storage saver quality began counting against account storage, while earlier qualifying uploads remained exempt. Google Docs-family files created or edited after that date also count, according to Google’s storage help page.

The old Gmail promise was “don’t worry about deleting.” The modern Google Account promise is more complicated: storage is shared, backups count, photos count under newer rules, account activity matters, and quota status can affect multiple services. A 5GB test accelerates that complexity into signup.

This is also a reminder that “free” cloud storage is not an eternal contract. It is a product policy. Google has changed storage rules before, often with advance notice and grandfathering. The 2020 Google Photos change ended a beloved unlimited backup model for new uploads after June 1, 2021. Google framed that as necessary to keep pace with growing demand and build the service for the future.

The Gmail storage test belongs to that same family of decisions. It does not delete the 15GB tier. It changes the conditions under which a new account receives it. That may sound minor from a legal-policy perspective, but it is meaningful from a user-trust perspective because the 15GB baseline was one of the clearest promises Google made.

The phone number is doing more work than the storage number

The most revealing part of the test is not the 5GB limit. It is the phone number. Google’s reported prompt does not say “upgrade to Google One.” It says users can unlock the larger storage allowance by using a phone number, and the message says the number helps make sure storage is added only once per person.

That line points to an anti-abuse model. Free accounts are easy to create. Free storage is costly when created at scale. A phone number raises the cost of mass account creation because it is harder to obtain and maintain than an email alias. It is not perfect. People can have several numbers, use virtual numbers, borrow a number, or rotate SIMs. But it is still a stronger signal than nothing.

Google already uses phone numbers in account verification. Its account help page says the company limits how many accounts each phone number can create to protect users from abuse. That gives the storage test a clear precedent: phone numbers are not just recovery tools; they are anti-abuse controls in the account-creation system.

The test turns that same control into a quota gate. Instead of only blocking suspicious account creation, the system can let an account exist while giving it a smaller storage grant until the user verifies with a phone number. That is a softer restriction than stopping signup, but it changes the product value.

For Google, this has obvious appeal. It reduces automatic storage exposure for accounts with weaker identity signals. It encourages recovery setup, which can reduce account-loss cases. It also helps discourage people or bots from creating endless accounts to harvest free storage. The phone number becomes a rationing device for free infrastructure.

For users, the calculus is different. A phone number is not just a login aid. It is a durable identifier that can follow a person across services, devices, carriers, and time. People worry about spam, SIM-swap risk, account lockouts after changing numbers, unwanted personalization, and the possibility that a number used for “security” might later be used for other Google services.

Google’s own support documentation recognizes different uses. A recovery phone number can help users regain access if they forget a password or lose access to an account. Google also lets users manage phone-number preferences, including a setting for “Better ads and Google services” that can allow a number to be used across Google services for more relevant ads, while users can turn that off.

That distinction will be central to trust. If Google says the number is needed only to ensure storage is added once per person and support recovery, users will ask whether the number is isolated for that purpose, whether it feeds other account systems, whether it can be removed later without losing storage, and whether refusal creates a durable second-class account.

The test’s wording, as reported, says Google will use the number to make sure storage is added only once per person. That is narrower than “we need your number for all account services.” Still, a phone number added to a Google Account exists inside a broader account data environment, governed by Google’s privacy controls and settings. The more valuable the reward, the more users will scrutinize the purpose boundary.

There is also a risk of user misunderstanding. Many people think of phone verification as temporary: receive a code, prove you are human, move on. A recovery phone number can persist. A user who adds a number to unlock storage may not know which settings to check after signup. If the storage reward is the main prompt, the privacy controls need to be easy to find.

This matters more in regions where phone numbers are hard to obtain, expensive, shared by families, recycled by carriers, or tied to identity documents. It matters for children and teenagers, low-income users, refugees, travelers, journalists, activists, people with abusive partners, and anyone who uses separate identities for safety. A phone number may be a routine account recovery tool for one user and a privacy boundary for another.

The test also interacts with Google’s move toward stronger account security. Google has been pushing passkeys, recovery options, and other ways to reduce account takeover risk. In 2025, Google introduced Recovery Contacts as another way for people to regain access when other methods are unavailable. That broader security direction makes the phone-number incentive easier to explain, but it does not remove the privacy debate.

The core tension is easy to state: Google wants a stronger signal that a storage grant belongs to a real, recoverable person; some users do not want a phone number to become the price of the full free tier. The test forces that trade-off at account creation, when users have the least context and the highest urgency to proceed.

The wording shift from 15GB to up to 15GB matters

Product policies often change first in language. Google’s current storage help page says each account includes up to 15GB shared across Gmail, Drive, and Photos. Google One’s plan page says all Google accounts come with up to 15GB of storage, included as part of the total storage offered in paid Google One plans.

The phrase “up to” is small but loaded. It means 15GB is the ceiling of the free included amount, not necessarily the amount every account receives automatically in every circumstance. In consumer-facing language, “up to” creates room for variation. In the context of the reported test, that room matters.

9to5Google reported that Google changed support-page language from “comes with 15GB” to “up to 15GB” and found the updated wording in the Internet Archive around March 2026. That is reporting from a tech publication rather than a Google announcement, but it aligns with the live wording on Google’s own pages.

This is the kind of change regular users may never notice until a signup screen makes it concrete. People do not read storage help pages before creating an account. They rely on remembered norms and product reputation. The help-page wording is where a company gives itself policy flexibility; the signup screen is where the user feels the shift.

From Google’s perspective, “up to 15GB” is cleaner if the company is testing different onboarding flows by region. It avoids a mismatch between help documentation and product behavior. It also fits promotional, special-purchase, and account-eligibility exceptions. Google’s storage page already says users may occasionally receive more storage from promotions or purchases.

From the user’s perspective, the change can feel like a downgrade in certainty. The old mental model was simple: create Google Account, get 15GB. The new wording says: create Google Account, get an amount that may be as high as 15GB. The difference is not just legal. It affects trust because users plan around defaults.

The same phrase appears on Google One’s plan page, where the free 15GB tier sits beside paid tiers such as 100GB and larger plans. If a new account sees 5GB by default, Google One’s pricing page still makes sense because it says up to 15GB. But the visual memory of a 15GB free tier remains strong.

This language also complicates coverage. Headlines saying “Google cuts Gmail storage to 5GB” are too broad. Headlines saying “Google tests 5GB default unless users verify by phone” are more accurate. But the deeper consumer issue is the wording shift from a guaranteed baseline to a conditional ceiling. The phrase “up to 15GB” is the policy architecture that lets the test exist.

The phrase also gives Google room to end the test, modify it, expand it, or apply it only in high-abuse regions. A company running a real-world experiment needs flexible documentation. But flexible documentation is rarely comforting to users because it removes a fixed expectation.

Search engines and answer engines will need care here. A direct answer such as “Gmail gives 15GB free” is now less complete than it was. The safer answer is: personal Google Accounts include up to 15GB of storage shared across Gmail, Google Drive, and Google Photos; Google is testing a flow in select regions where some new accounts start with 5GB unless a phone number is added. That answer preserves both the official wording and the current test.

This also shows how product documentation can become news. No pricing page needs to announce “we cut storage.” A new qualifier can do much of the same work. Users may not object to experimentation. They object when the product norm changes without a clear public explanation.

For Google, the risk is not only negative coverage. It is fragmentation of the account promise. If users in one region get 15GB automatically, another gets 5GB plus phone unlock, and another is forced to add a phone number during signup before ever seeing the choice, the public understanding of Google Account storage becomes messy. Support forums then fill with conflicting answers, and media coverage has to hedge.

That mess may be temporary if Google resolves the test quickly. It becomes a problem if “up to 15GB” remains the official line while the actual signup experience varies widely. A storage benefit is easiest to trust when it is easy to explain.

The real product affected is the Google Account, not only Gmail

Many headlines say Gmail because Gmail is the product people know. The storage pool, however, belongs to the Google Account. Google’s support pages say the quota is shared across Gmail, Google Drive, Google Photos, WhatsApp backups on Android, and certain files created or edited in collaborative apps.

That distinction changes the stakes. A new Gmail account is often a new Google identity. It may become the login for Android, Play Store purchases, Chrome sync, YouTube, Drive documents, Calendar events, Docs files, Meet links, Google Photos backups, password manager data, and recovery settings. The quota sits underneath that identity.

A 5GB default can therefore shape how new users try Google services. They may avoid Photos backup because the storage bar looks small. They may delete Drive files earlier. They may treat Gmail attachments as a quota threat. They may buy Google One sooner. Or they may add a phone number and never think about it again.

For Google, this is a classic onboarding decision: reduce abuse while preserving low-friction adoption. The company has to avoid making the first experience feel cramped. Gmail is still a strong service, but a new account that immediately shows a storage limit below the long-known 15GB value may feel less generous than expected.

The effect will be uneven. Users who create a Google Account only for email and do not use Photos may not care. Users who create an account on an Android phone may care a lot, because Android setup nudges people toward backups, Photos, Drive, Play, and device continuity. A 5GB quota can look small once phone photos and backups enter the picture.

Google’s support page says that when an account is full, the user may be unable to upload or create Drive files, send or receive Gmail messages, or back up photos and videos to Google Photos. That is severe because storage exhaustion is not isolated to one product.

A shared quota makes storage a system-wide reliability issue. If Gmail stops receiving messages because Photos or Drive consumed the pool, the user does not experience that as a neat product boundary. They experience it as Google failing at email. That is one reason the free baseline is so sensitive.

This is also why 15GB has worked well as a buffer. It gave users space to be casual. It allowed Google to cross-promote products without making the quota feel immediately punitive. A 5GB default removes much of that buffer, unless the phone-number unlock is accepted.

The test could also alter user behavior around account multiplication. People have long created separate Google Accounts for roles: personal, school, side projects, newsletters, testing, family devices, small businesses, anonymous publishing, and backups. Some of those uses are legitimate. Some are abusive. Google’s one-storage-grant-per-person logic aims at abuse, but it will also affect legitimate compartmentalization.

If each account needs a phone number to receive 15GB, people who maintain separate identities may face a choice: attach the same number where allowed, use smaller quotas, or pay. Google already limits how many accounts can be verified with one number. That means a person with many legitimate accounts may not be able to unlock 15GB on all of them.

This is where product policy becomes identity policy. Google is not merely assigning disk space. It is deciding whether multiple accounts should receive multiple full free grants. The test suggests the answer may be no, at least where Google cannot tie those accounts to a verified person.

The company’s anti-abuse logic is understandable. Without limits, free storage can be harvested. But consumers often use account separation as a privacy and safety technique. A journalist may separate sources from personal life. A small-business owner may separate client work. A parent may create an account for a child’s device. A developer may test services. A person leaving a harmful relationship may need a new account not tied to old recovery details.

A policy aimed at bots can still burden edge cases. The quality of the policy will depend on exceptions, clarity, and whether users can appeal or understand limits. If the rule is invisible until signup, frustration rises.

The most practical reading is that the Google Account is moving toward stronger identity anchoring. Storage is the incentive. Gmail is the brand name in the headline. But the real subject is the account layer that ties Google’s consumer ecosystem together.

Five gigabytes is enough for email until it suddenly is not

Five gigabytes can hold a lot of plain email. Text is small, and even years of ordinary messages may not reach the limit quickly. The problem is that modern email is not plain text. Attachments, embedded images, PDFs, videos, invoices, school files, newsletters, exported reports, shared document notifications, and app-generated messages can accumulate quietly.

Gmail storage also includes Spam and Trash folders, according to Google’s storage documentation. That surprises users because deleting a message does not necessarily free quota until Trash is emptied, and spam still occupies space while retained.

Drive and Photos change the math further. A few phone videos can consume gigabytes. A WhatsApp backup can be large. A shared school project can bring in PDFs and slides. A user who sees “5GB” may think “email,” but Google’s quota system sees account-wide storage.

For a light user, 5GB may last. For a new Android user who turns on backups and Photos, it may not. For a student, freelancer, or family account, it can feel cramped. The difference between 5GB and 15GB is not only 10GB; it is the difference between a casual account and a monitored account.

Google’s own storage-management article recommends deleting large emails, emptying trash and spam folders, removing duplicate Drive files manually, checking backups, and managing WhatsApp backup size. Those are reasonable steps for someone already managing a mature account. They are a lot to ask of a new user who thought Gmail storage was generous by default.

A smaller quota also changes what “free” feels like. Free services often work by giving users enough room to build habits, then charging when habits grow. That is not inherently unfair. Cloud storage costs money, and paid tiers are normal. But a 5GB default creates a shorter path from signup to quota anxiety.

There is another behavioral effect: users may avoid deleting data because they fear losing records, yet they may not understand what counts. Google Drive files in Trash count until permanently removed. Gmail attachments count. Photos may count depending on upload date and quality. Files created or edited after certain dates count under Google’s newer storage rules. Complexity makes people more likely to pay than manage.

From Google’s business perspective, that is useful. Google One is the paid storage answer. Its consumer plans add more space across Gmail, Drive, and Photos, with 100GB as a common entry tier and larger plans for heavier users. Google One also bundles family sharing and other benefits depending on plan and region.

But the current test is not a direct paywall. It is a verification wall. A user can reportedly receive the full 15GB at no cost by adding a phone number. That makes the decision more delicate. If the user refuses, the smaller quota may feel like a penalty for privacy. If the user accepts, Google gets a stronger account signal. If the user pays later, Google gets revenue.

The 5GB number is also competitive symbolism. Apple has been criticized for keeping iCloud’s free tier at 5GB despite the growth of iPhone backups and photos. Microsoft’s free OneDrive cloud storage also starts at 5GB. Google’s 15GB has been a simple way to say its free cloud offer is larger. A 5GB default weakens that story, even if the unlock remains free.

The question is not whether 5GB is objectively enough. There is no single answer. The question is whether 5GB is enough to preserve the product expectation Google spent years building. For many users, the answer will be no.

The most likely user split is clear. Privacy-sensitive users will resent the phone-number condition. Storage-heavy users will add the number quickly. Light users may keep 5GB and never care. Power users will already have Google One or other storage systems. The people most likely to feel squeezed are those who need a new account, need privacy, cannot easily use a phone number, and still need a realistic quota.

That group may not be the majority. But it is exactly the group most likely to talk about the change publicly.

The storage test fits a long pattern of free-tier tightening

Google has changed storage rules before. The most obvious example is Google Photos. In November 2020, Google announced that new high-quality Photos uploads after June 1, 2021 would count toward account storage, while earlier high-quality uploads would remain exempt. Google framed the change as a way to keep pace with growing storage demand and build Photos for the future.

That decision reshaped the meaning of the 15GB pool. Before the change, many users treated Photos backup as separate from quota if they used the compressed “High quality” setting. After the change, new uploads counted. The same 15GB free pool now had to absorb more daily life.

Google also updated policies around inactivity and over-quota accounts. Its storage help page says that if an account remains over quota for two years or longer, content across Gmail, Photos, Drive, Docs, Sheets, Slides, Drawings, Forms, Vids, and Android backups may be removed after notice and an opportunity to act.

The company also has an inactive account policy. Google says it reserves the right to delete a personal Google Account and its data if the account is inactive across Google for at least two years. Google announced the updated inactive-account policy in 2023, citing security risks from abandoned accounts.

These changes point in one direction: Google is managing storage and abandoned identity more tightly. It is not alone. Cloud companies have become less casual about free capacity, dormant accounts, and unlimited backup promises. The era of “store everything forever for free” has been narrowed by cost, security, compliance, and abuse.

The 5GB test is different because it affects the front door. Google Photos’ 2021 change affected new uploads. Inactive-account rules affect accounts left unused. Over-quota rules affect users who exceed their allowance. The new test affects a person at the moment they create an account.

That makes it feel sharper. A new user has not abused storage yet. They have not filled an account. They have not gone inactive. They are being asked to verify before receiving the long-known full free allowance. The policy is preventive rather than corrective.

Preventive controls are common in security. They are also harder to explain because they treat users according to risk before any user-specific behavior is visible. Google is likely looking at regional abuse patterns, account-creation signals, device context, IP reputation, phone availability, and other internal factors. Users see only the result: 5GB or 15GB.

The pattern also mirrors a broader shift in digital services. Free tiers increasingly use friction to separate humans from bots and casual users from committed users. Some services limit features until a phone number, card, device, or identity signal is added. Others reduce API access, file size, model usage, or collaboration limits. The point is to protect infrastructure from unlimited free consumption.

Storage is especially sensitive because it accumulates. A search query is transient. A photo backup stays. A spam account with stored files imposes ongoing cost. A dormant account can carry data risk for years. The more accounts a platform supports, the more storage grants become a liability.

That does not mean users should ignore privacy concerns. It means the change should be analyzed as a resource-governance decision, not only a monetization trick. Google’s test can be seen as anti-abuse, security, cost control, Google One funnel design, and identity consolidation at the same time. The weight of each motive is not public.

The company’s own confirmed statement emphasized service quality, account security, and data recovery. It did not say the test is about pushing Google One subscriptions. A fair analysis should not claim a paid-storage motive as fact. It can say the test may have revenue side effects because smaller default quotas shorten the path to paid plans for users who do not verify or who fill storage quickly.

The long pattern is the stronger evidence. Google has steadily moved from abundant, loosely metered consumer storage toward measured, shared, managed storage. The 5GB test is a new expression of that older direction.

Google One becomes more central even when the test is not a paywall

Google One is the obvious commercial backdrop. Google’s paid storage plans increase the quota shared across Gmail, Drive, and Photos. Its current plans page says all Google accounts come with up to 15GB and then presents paid tiers such as 100GB, 2TB, and larger AI-linked plans depending on market.

The 5GB test does not require users to pay for 15GB. That is crucial. If users add a phone number, they can reportedly unlock the full 15GB at no cost. But Google One still becomes more central because a smaller default allowance makes storage visible earlier.

Storage anxiety is one of the strongest subscription triggers in consumer software. People pay when they are afraid of losing email, missing incoming messages, failing to back up photos, or being unable to upload work files. Google’s own help pages warn that over-quota accounts may lose key functions, including Gmail send/receive behavior and Drive uploads.

Even if the test is mainly anti-abuse, it can improve the Google One funnel. A user who keeps 5GB may reach the paid decision sooner. A user who unlocks 15GB by adding a phone number becomes a more secure, recoverable, and possibly more engaged account. Both outcomes are better for Google than unlimited anonymous account creation with automatic 15GB grants.

This is why the test is strategically clever. Google does not have to choose between charging and verifying. It can use storage as a fork. The privacy-sensitive user who refuses verification gets a smaller free allowance. The convenience-focused user gives Google a stronger identity signal. The storage-heavy user eventually pays. The test routes different user types into different levels of cost, trust, and revenue.

The risk is that users notice the routing. If the prompt feels like a reward for safety, it may be accepted. If it feels like a privacy tax, it may generate backlash. The wording of the prompt is therefore not cosmetic. “Improve account recovery” lands differently from “Google will use your phone number to make sure storage is added only once per person.” The first emphasizes user benefit. The second emphasizes quota enforcement.

Google’s statement to Android Authority used both ideas: service quality, account security, and data recovery. The reported signup prompt leaned into one-storage-grant-per-person. Those are related but not identical narratives.

Google One’s value has also been changing. It is no longer only a bucket of storage. Higher tiers have become tied to AI features, Gemini access, Photos editing features, family sharing, and other benefits that vary by region and plan. The free storage baseline sits at the bottom of a bundle ladder. A smaller default tier can make that ladder steeper.

For a company at Alphabet’s scale, even small conversion changes can matter. But the more defensible reason to test this may be abuse prevention rather than immediate subscription revenue. A bot farm exploiting automatic 15GB grants can create storage costs without converting to paid plans. A phone-number gate directly targets that problem.

The consumer impact is still real. When an account is close to full, Google One becomes the cleanest answer. Storage management takes time, and deleting personal data is emotionally hard. Paying a small monthly fee may feel easier. That is the power of cloud subscription economics.

Google must be careful not to blur verification and purchase pressure. If users believe phone-number refusal is being used to push paid plans, trust suffers. If Google offers clear choices—keep 5GB, add number for 15GB, or buy storage later—the policy is easier to defend. If those choices vary by region or are hidden in account setup, confusion will grow.

The test may also push privacy-conscious users to competitors. Yet competitors often offer less free storage by default. Apple and Microsoft both provide 5GB cloud-storage starting points in core consumer offerings; Dropbox Basic is 2GB. Proton’s privacy-first pitch comes with a smaller default Drive allowance that can be increased through setup actions. The market does not offer a perfect substitute for “15GB free with no phone number.”

That gives Google room. It can tighten the free tier and still remain competitive if 15GB is easy to unlock. The danger is not users leaving en masse. The danger is a trust downgrade: people may stay but become more skeptical of Google’s account promises.

Account abuse gives Google a defensible reason

Free account systems attract abuse. That is not a theory; it is an operating reality for every large platform. Email accounts are used for spam, fraud, credential stuffing, fake reviews, phishing, bot signups, disposable identities, and storage exploitation. Storage quotas can be abused as free file hosting or backup capacity across many accounts.

Google’s help page for account verification says it limits how many accounts each phone number can create to protect users from abuse. That sentence gives the company a straightforward policy basis for using phone numbers as an anti-abuse signal.

The new storage test appears to apply that logic specifically to quota allocation. Instead of treating every new account as equally entitled to the largest free allowance, Google can reserve the full free grant for accounts with a stronger identity signal. That is a resource-control design.

From an infrastructure perspective, automatic 15GB grants are risky because the liability is multiplied by every account created. Most users may never use all 15GB. But abuse economics depend on scale. If automated account creation can produce many 15GB pools, the free tier becomes a storage subsidy for actors Google does not want.

Phone numbers are a blunt tool, but blunt tools are common in abuse prevention because they work at scale. They introduce cost, scarcity, and traceability. They also create false positives and burdens for legitimate users. The question is not whether phone verification reduces abuse; it is whether storage should be the lever used to demand it.

Google may prefer this design because it avoids excluding users entirely. An account without a phone number can still exist with 5GB in the tested flow. That is less harsh than refusing signup. It also lets Google keep access open in cases where phone verification is not available, while reducing the resource granted to lower-confidence accounts.

This is an elegant compromise for Google, but not necessarily for everyone else. A user may say: “If I am allowed to create the account, why am I not allowed the same free storage?” Google’s likely answer is: “Because storage is a scarce resource and phone verification helps limit repeated grants.” That answer is rational, but it reframes free storage as per-person, not per-account.

Per-person logic is a major shift. The internet has long allowed one person to maintain many accounts for legitimate reasons. Google’s reported prompt says the phone number helps ensure storage is added only once per person. That implies the full 15GB is not intended as an endlessly repeatable account benefit. It is a human benefit.

The difficulty is implementation. People share phones. Phone numbers are recycled. Some users have no reliable SMS access. Some regions have higher fraud rates. Some privacy-focused users intentionally avoid phone-number linkage. A per-person rule enforced through phone numbers will never map cleanly onto real human identity.

Google likely knows that. The goal is not philosophical perfection; it is abuse reduction. But product policies that touch identity need transparency because the failures are personal. A false block on storage may be annoying. A false block on account recovery can be devastating.

The company can reduce backlash by publishing plain rules. Which regions are in the test? Are existing accounts affected? Can users remove the phone number after unlocking 15GB? Does storage fall back to 5GB if the number is removed? Can the same number unlock 15GB for more than one account? What happens when a phone number is recycled? Are virtual numbers accepted? Is there an alternative verification method?

Without answers, users fill the gaps with suspicion. Some will assume the goal is ad targeting. Some will assume Google is preparing a paid-tier squeeze. Some will assume existing accounts are next. Clear policy language would limit speculation.

The strongest defense Google has is the abuse-prevention case. The weakest part is the lack of a broad public explanation at the time the test was noticed. A confirmed statement to one publication is useful, but a product as large as Gmail deserves a direct help-page explanation if the test expands.

Privacy objections are not paranoia

Users who object to the phone-number condition are not being irrational. A phone number is a sensitive account attribute. It can be used for recovery, verification, anti-abuse, messaging, personalization, and cross-service recognition. It can also become a risk if a carrier account is compromised, a SIM is swapped, or a number is recycled.

Google’s support pages show that phone numbers have several account roles. Users can add a recovery phone number to regain access. They can manage phone number settings. They can control preferences related to “Better ads and Google services.” Google’s privacy policy says users can manage contact information such as name, email, and phone number.

That does not mean Google is misusing phone numbers in this test. It means users have a valid reason to ask for boundaries. If a number is collected to enforce one storage grant per person, the user will want to know whether it is used only for that purpose, also for recovery, also for account security, or also elsewhere depending on settings.

Privacy law and norms make that question sharper. The UK Information Commissioner’s Office explains the data minimisation principle under the UK GDPR as requiring personal data to be adequate, relevant, and limited to what is necessary for the purpose. A phone number can be necessary for certain anti-abuse or recovery purposes, but the platform must be clear about the purpose.

For users, the concern is partly about control. If a phone number is optional, users can decide. If the practical cost of refusing is a smaller storage allowance, the option feels less free. The more valuable the benefit being withheld, the more the choice looks like pressure.

This is not unique to Google. Many services use dark patterns, nudges, rewards, or friction to collect more data. Google’s test is not automatically a dark pattern, but it sits near that line because the long-known expectation was 15GB. Users may see the phone-number prompt not as a bonus but as a condition attached to something they already believed was included.

A privacy-respecting implementation would make the trade-off explicit, narrow, reversible, and easy to understand. The prompt should say what the number is used for, whether it is used for recovery, whether ad-related uses are separate, what happens if the number is removed, and whether alternatives exist.

People also have security concerns about phone numbers. SMS-based verification has known weaknesses, including SIM swapping and carrier dependence. Google itself has been moving toward stronger methods such as passkeys and recovery contacts. That makes it slightly awkward to make phone numbers the gate for storage. The company can argue that phone numbers remain useful for abuse prevention even if they are not the ideal authentication factor.

There is a difference between using a phone number as a recovery option and using it as proof of uniqueness. Recovery helps the account owner. Uniqueness helps the platform allocate resources. The same data point serves both sides, but the user benefit is not identical.

The criticism will also vary by region. In places where phone numbers are closely tied to government ID, adding a number may feel like a stronger identity surrender. In places where prepaid SIMs are common and cheap, it may feel routine. In places where numbers are reused frequently, recovery risks can rise. A global service has to handle all of those realities.

Google can also point out that many account-creation flows already require phone verification in practice. Android Authority noted that in one account-creation attempt, Google would not let the writer continue without adding a phone number, while other cases may not require it, such as certain Android setup paths. That makes the storage prompt part of a wider, inconsistent phone-verification experience.

Inconsistency is where suspicion grows. If some users are forced to add a phone number to create an account, some are offered 5GB or 15GB, and some receive 15GB automatically, the rule feels opaque. Opaque privacy trade-offs are the ones people trust least.

New accounts are the test bed because existing accounts are risky to touch

Google appears to be testing this on new accounts, not retroactively downgrading existing ones. That choice is predictable. Existing users have expectations, stored data, and reliance. Reducing their storage from 15GB to 5GB would create immediate harm, support costs, and public backlash.

New accounts are easier. They have no stored data yet. The user can be shown the rule at signup. The account can be classified into a storage tier before behavior begins. Policy changes are much cheaper at onboarding than after users have built their lives around a quota.

Google has a history of grandfathering storage changes. With Google Photos, uploads made before the June 1, 2021 change under eligible quality settings remained exempt. That reduced the sense of broken promises, even though new uploads began counting.

A similar pattern may apply here if the test expands. Existing accounts may keep their 15GB. New accounts may face conditional rules. That would be the least disruptive path. It would also create a two-class account system for years, where older accounts enjoy simpler terms and newer accounts face identity-based storage unlocks.

Two-class systems are common in tech. Early users keep legacy plans. New users get revised tiers. The tension comes when users compare notes. Someone creating an account for a child, parent, employee, club, or side project may wonder why the new account has less than their old account.

Google may also be trying to avoid legal and reputational issues. Users with existing data could claim reliance on the 15GB free allowance. Even if Google’s terms allow changes, a retroactive cut would look harsh. New-account conditions are easier to defend because the user sees the terms before storing data.

That does not make the test consequence-free. Gmail accounts are often created because someone needs access immediately: a phone setup, job application, school assignment, recovery address, government form, online purchase, or collaboration invite. In those moments, a phone-number condition can feel coercive because the user needs the account now.

The test could be especially awkward for families. A parent creating an account for a child may not want to attach a phone number. A person helping an elderly relative may not want to use their own number and risk future recovery confusion. A small organization may create role accounts and not want them tied to one individual’s phone.

Google’s one-per-person storage logic does not map neatly to shared or delegated account creation. If a family has several members but one phone number, how many accounts receive full storage? If a small business uses personal accounts incorrectly, does the policy push it toward Workspace? That may be good from a compliance standpoint, but the user may not see it that way.

The test may also affect disposable or low-trust account creation. Google probably wants that. Accounts created for spam, trial abuse, scraping, or storage harvesting are more likely to avoid phone verification. A 5GB cap reduces the reward. If that is the goal, new accounts are exactly where the control belongs.

The key point is that Google can avoid the most explosive backlash by leaving existing accounts alone. But it cannot avoid the broader debate if new accounts become conditional everywhere. Gmail’s reputation is built across generations of users. A new-user downgrade still changes the brand promise.

The comparison with Apple, Microsoft, Dropbox, and Proton is more complicated than it looks

On a raw number chart, Google’s tested 5GB default looks less special. Apple gives 5GB of free iCloud storage. Microsoft’s free consumer offer includes 5GB of OneDrive cloud storage, though Outlook mailbox storage is separate in Microsoft’s plan presentation. Dropbox Basic offers 2GB. Proton Drive can reach 5GB after completing welcome actions, according to Proton’s support page.

Free consumer cloud storage comparison

This comparison is useful but incomplete. Storage value depends on what counts, how tightly the quota is tied to a device ecosystem, whether email is included, whether photos are included, how easy export is, and what happens when the account is full.

Apple’s 5GB iCloud tier is often criticized because iPhone backups, iCloud Photos, messages, app data, and device continuity can make 5GB feel tiny. But iCloud is deeply integrated into Apple devices, and users often pay because backup failure is stressful. Google’s 15GB has looked generous partly because it is three times Apple’s free number. A 5GB default would reduce that contrast.

Microsoft’s structure is different. The free Microsoft 365 consumer page lists 5GB of cloud storage and 15GB of mailbox storage. That split means a OneDrive file quota comparison does not perfectly match Google’s shared pool. Google’s single pool is simpler but can create cross-product pressure.

Dropbox is more specialized. Its 2GB Basic tier is small, but Dropbox is not the default email, Android backup, or photo identity layer for billions of users. A small Dropbox allowance feels like a file-sync trial. A small Google Account allowance affects a wider identity bundle.

Proton’s model adds a useful contrast. Proton Drive’s free storage can be increased by completing onboarding actions, which means Proton already uses activity gates to expand free capacity. The difference is that Proton’s brand centers on privacy, and the gate described in its support article is a welcome checklist rather than a phone-number identity condition.

The comparison shows that 5GB is not an outlier in the market. It is an outlier for Google’s own history. The problem for Google is not that 5GB is unheard of; it is that 15GB became part of Gmail’s identity.

A smaller default also changes Google’s competitive message in developing markets. Android is the first computing platform for many users, and a Google Account is often their first durable cloud identity. If the full storage grant requires phone verification, users without stable numbers may receive a weaker starting experience than users with stable mobile access.

Competitors may use this in messaging. Privacy-focused providers can say Google is making users trade a phone number for storage. Apple can point out that Google now also starts at 5GB in some cases. Microsoft can emphasize separated mailbox and cloud storage. Dropbox can avoid the identity debate by staying focused on files. Proton can contrast privacy posture.

Still, switching costs are high. Gmail addresses are identity anchors. Google Docs collaboration is common. Android setup expects a Google Account. YouTube and Play are tied into the same identity. Storage complaints rarely cause immediate mass migration because email and cloud identity are sticky.

The competitive pressure may therefore be reputational rather than churn-driven. Google’s free tier may still be good. It may just feel less clean.

The business logic is tied to infrastructure discipline

Alphabet’s infrastructure spending is the backdrop to every storage conversation, even when a specific consumer policy is not directly caused by it. In Q1 2026, Alphabet said capital expenditure was $35.7 billion, with the overwhelming majority going to technical infrastructure for AI opportunities. The company said about 60% of technical infrastructure investment in the quarter went to servers and 40% to data centers and networking equipment.

Google Cloud also reported strong growth. Alphabet’s Q1 2026 materials said Google Cloud revenue increased 63% to $20.0 billion, led by Google Cloud Platform growth across enterprise AI solutions, enterprise AI infrastructure, and core GCP services. Sundar Pichai’s Q1 remarks said Cloud backlog nearly doubled quarter over quarter to over $460 billion.

Those numbers do not prove that Gmail’s storage test is a cost-cutting response to AI. It would be sloppy to claim that. Consumer Google storage, Google Cloud infrastructure, AI model training, and data-center capex are related through broad infrastructure planning but not identical cost centers.

They do show a company allocating enormous capital to servers, data centers, networking, AI services, and cloud customers. In that environment, free consumer storage is less likely to be treated as an unlimited goodwill expense. Every gigabyte promised to a low-trust, inactive, or duplicate account is still part of a resource system.

Storage costs have also become more strategically visible across the industry. AI workloads increase pressure on data centers, memory, and storage supply chains. Hyperscalers are spending heavily. Investors now watch capex closely. A free 15GB grant to every new account may look small at user level but large when multiplied by account volume and abuse.

Google’s stated rationale in the confirmed test was service quality, account security, and data recovery. The “service quality” phrase is broad enough to include infrastructure pressure without saying “cost.” A company can maintain service quality by reducing abuse, improving account recoverability, managing storage allocation, and shifting heavy users to paid tiers.

From a business standpoint, the test has several potential advantages:

• It lowers the default storage commitment for accounts that do not provide a stronger identity signal.
• It encourages phone-number recovery setup, reducing account-loss problems.
• It limits repeated full storage grants to one person across many accounts.
• It preserves a “15GB free” story for users willing to verify.
• It may increase Google One relevance for users who stay at 5GB or fill storage quickly.

The main business risk is trust. A storage policy that looks like a stealth rollback can make users question future account terms. Google can absorb some anger, but Gmail is a core trust product. People keep legal notices, medical messages, school records, job applications, family photos, and financial documents in Google services. Quota policy feels personal because the data is personal.

Infrastructure discipline is rational. Trust erosion is expensive. The strategic question is whether Google can get the former without triggering too much of the latter.

The cleanest path would be transparency: publish a help article explaining the test, regions, eligibility, phone-number use, alternatives, effects on existing accounts, and how to manage the number later. That would turn a rumor-led story into a policy-led story. It would also give publishers and search engines a stable source to cite.

Without that, coverage will rely on screenshots, third-party testing, and a statement to Android Authority. That is enough to confirm the test, but not enough to settle user concerns.

The test may reduce spam and storage farming, but it will not stop all abuse

Phone-number verification is a speed bump, not a wall. Abuse actors can buy numbers, use SIM farms, exploit virtual-number providers, borrow numbers, or shift to other services. The question is not whether the test eliminates abuse. It is whether it changes the economics enough to be worth the user friction.

For mass account creation, every added cost matters. If an abusive actor wants thousands of accounts, requiring a unique or acceptable number for each full 15GB grant raises the cost sharply. If unverified accounts receive only 5GB, the actor gets one-third of the storage for the same account-creation effort. That alone may deter storage farming.

The one-per-person framing also gives Google more policy authority to limit repeated grants. A person who tries to create dozens of accounts for free storage can be told the full allowance is not meant to be multiplied endlessly. That is easier to defend than vague “suspicious activity” language.

But legitimate users can be caught in the same net. A person may create multiple accounts for privacy compartmentalization, not storage farming. A family may use one phone number across several accounts. A user may have a number that Google rejects because it has been used before. Google’s account verification help already warns that a phone number may not be usable if it has reached limits.

The test’s quality will depend on how it handles such cases. A rigid system will produce support pain. A flexible system will be easier to abuse. Large platforms live inside that tension.

The storage-farming problem also differs from spam. Spammers may care more about sending volume and account reputation than storage. A 5GB cap may not deter them much. But it can reduce the value of accounts created for file storage, photo backup, data dumping, or resale.

Google may combine this with other risk signals. The phone-number prompt may appear only in select regions or account flows because Google’s internal risk scoring determines where it is needed. That would explain why some users see it and others do not. It would also make the policy harder to explain publicly because the rules may be dynamic.

Dynamic abuse controls are effective but opaque. Users are used to CAPTCHA, device checks, login challenges, and phone verification appearing unpredictably. Storage quotas, however, feel like product terms. People expect them to be stable. Mixing dynamic risk scoring with quota size creates confusion.

A security check can be unpredictable; a storage promise should not feel unpredictable. That is the challenge Google has created by using storage as the reward.

If the test works, Google may see lower account abuse, better recovery setup, and limited user loss. If it fails, the company may see public backlash, support confusion, and accusations that it is using privacy pressure to preserve margins. The outcome depends less on the technical logic than on the clarity of the policy.

Search, AI answers, and publishers need careful wording

This story is a trap for oversimplified answers. A search snippet that says “Google has cut Gmail storage to 5GB” is too broad. A snippet that says “Gmail still gives 15GB free” is now incomplete. The accurate answer must include the test, the phone-number unlock, new-account scope, select-region language, and the official “up to 15GB” wording.

A strong answer is: Google has confirmed a test in select regions where some new accounts receive 5GB of free storage by default and can unlock 15GB at no cost by adding a phone number; Google’s official storage pages describe free account storage as up to 15GB shared across Gmail, Drive, and Photos. That is the cleanest short form supported by current evidence.

This matters for Google News and AI answer systems because the difference between “test” and “policy” is material. Users may be creating accounts today and want practical advice. They do not need panic. They need the current state.

The story also exposes a contradiction for Google as both subject and distributor of news. Google Search, Discover, AI Overviews, and other answer surfaces may summarize a Google policy change based on third-party reporting and Google support pages. If Google does not publish a clear primary explanation, its own information ecosystem will rely on outside interpretation.

For publishers, the best coverage should avoid three errors. First, do not imply existing accounts are losing 10GB. There is no public evidence for that. Second, do not imply the 15GB tier now costs money. The reported unlock is free with phone-number verification. Third, do not dismiss privacy concerns as overreaction. Phone-number collection is a real data issue.

The story also needs exact dates. 9to5Google reported the new-account prompt on May 14, 2026. Android Authority updated its story on May 15, 2026 with Google’s confirmation. Google’s 15GB unified storage promise dates to May 2013. Google Photos’ storage-policy change took effect for new uploads on June 1, 2021. These dates show the progression from generous unified storage to more managed account storage.

Semantic precision also matters. It is not just “Gmail storage.” It is “Google Account storage shared across Gmail, Google Drive, Google Photos, and other counted data.” Users searching for Gmail may still need that broader explanation because Gmail send/receive behavior can be affected when the shared quota is full.

Another wording issue is “free.” The 15GB unlock is reportedly free in money terms. It is not free in data terms if the user must provide a phone number. Writers should avoid treating those as identical. A good phrase is “at no monetary cost after phone-number verification.”

This is also a useful example for answer engines: users may ask, “Does Gmail still give 15GB?” The best answer is conditional, not evasive. Yes, Google still describes accounts as including up to 15GB, and the full 15GB remains available in the tested flow after phone-number verification. No, some new accounts in the test may not receive 15GB automatically.

A clear FAQ is not enough. The main article should repeat the scope because many readers scan. The words “new accounts,” “select regions,” “test,” “phone number,” and “up to 15GB” need to appear near the top and throughout the analysis.

The user impact depends on the kind of account being created

A new account is not always the same type of account. Someone may create one for a personal inbox, a child’s phone, a school project, a side business, a YouTube channel, a Drive collaboration, a job hunt, or a recovery email. The 5GB test affects each case differently.

For a basic email account, 5GB can last for years if the user avoids large attachments and does not use Photos or Drive heavily. For a Google Photos account, 5GB can disappear quickly. For Drive collaboration, file size and editing habits matter. For Android backups, device and app settings matter. For WhatsApp backups, video inclusion can be decisive. Google’s Drive help page specifically notes that WhatsApp backups on Android count toward Google Account storage and can become one of the largest storage items.

For children’s accounts, the phone-number prompt can be awkward. A child may not have a phone number. A parent may not want to attach theirs. If the account receives only 5GB, photo backups, school files, and device usage may become constrained. Google has separate family and child-account systems, but the storage question may still surface in ordinary account creation.

For privacy-sensitive users, the 5GB default may be acceptable if they use the account only for low-volume email. The problem is loss of parity. They may feel they are receiving a lesser account because they protected a personal identifier.

For small businesses, the test may be a nudge away from informal personal-account use. Google would likely prefer businesses to use Workspace, where storage, identity, admin controls, and support are managed differently. Google Workspace’s consumer comparison is outside this account test, but the broader direction is clear: personal free accounts are not meant to be an unlimited substitute for organizational infrastructure.

For developers and testers, 5GB may not matter. But phone-number limits may create friction if they need multiple accounts. Testing across products often requires separate identities. Google may have internal paths for developers, but ordinary users do not.

For people in vulnerable situations, account separation can be safety. A new Google Account may be needed to escape monitoring by a partner, employer, family member, or hostile group. A phone-number requirement can create linkage or recovery risk if the number is known, shared, or controlled by someone else. A 5GB allowance may be enough for a safety account, but the principle matters.

For journalists and activists, phone-number linkage can be sensitive. The ability to create a fully useful account without a durable phone identifier has practical value. A storage penalty may not block use, but it reduces capability.

For users in countries with frequent SIM churn, number recycling creates recovery problems. A phone number that helps today may become a liability if reassigned. Google can mitigate this through account recovery options, passkeys, recovery contacts, and prompts to keep numbers current, but the risk remains.

The common pattern is this: the storage test is easiest for mainstream users with stable mobile numbers and hardest for people who need account separation, anonymity, shared-device access, or low-friction new identities.

Product teams often design for the majority case. Policy teams have to watch the edge cases because that is where harm clusters. If Google expands the test, the exceptions and alternatives will matter as much as the default.

Existing users should not panic, but they should check their storage habits

There is no current evidence that existing personal Google Accounts are being reduced from 15GB to 5GB under this test. Existing users should not panic-delete files or assume their inbox is about to stop. The confirmed test is about new accounts in select regions.

That said, the news is a useful prompt to review storage. Google’s own tools show how much storage is used by Gmail, Drive, Photos, and other categories. Google recommends clearing Trash and Spam, deleting large emails, reviewing Drive storage, and managing backups.

The practical advice is straightforward. Check the Google One storage manager. Look for large Gmail attachments with search operators such as has:attachment larger:10M, which Google’s help page itself recommends. Empty Trash only after confirming you no longer need the files. Review Google Photos backup settings. Check Android WhatsApp backup size if you use WhatsApp.

Users should also understand over-quota consequences. Google says over-quota accounts can lose the ability to upload Drive files, back up photos, and may have Gmail send/receive behavior affected. If over quota for two years or longer, content may be removed after notice and an opportunity to act.

That policy is not new, but a smaller new-account allowance would make it more relevant for future users. Existing users near 15GB may already face the same quota-pressure mechanics, even if their account was not part of the 5GB test.

A good personal storage routine is boring but useful: keep a local export of critical files, do not treat any free cloud tier as permanent archive storage, maintain current recovery options, and know which products are using the quota. Google Takeout remains an option for exporting data, and Google’s storage help pages direct users to download data before deletion risk.

Users who refuse phone-number linking on principle should be more intentional. If creating a new account in a tested region, assume 5GB may be the starting quota. Use it for email or light Drive work, not photo backup. Consider a separate privacy-focused provider for files. Keep local copies of anything critical. Do not wait until the account is full to plan.

Users who do add a phone number should review account settings afterward. Check recovery options, ad and personalization preferences, and whether the number is visible or used across services. Google provides settings for managing phone numbers and related preferences.

The decision is personal. For many people, adding a phone number will be a reasonable trade. It improves recovery and unlocks the larger free allowance in the tested flow. For others, the phone number is not worth the privacy cost. Both choices are valid.

What users should not do is treat Gmail as infinite. The storage era that encouraged people to keep everything has been replaced by a managed-quota era. That was already true after the Photos change. The 5GB test makes it harder to ignore.

The change would matter most in Android onboarding

Android is where this policy could have the largest practical effect. Many new Google Accounts are created during device setup. A user may be trying to activate a phone, restore apps, access Play, sync contacts, set up Photos, and enable backups. Storage is not the only consideration, but it becomes part of the first-run experience.

If a user sees 5GB during Android setup, the account feels constrained before the phone is fully usable. If they add a phone number, the full 15GB appears. That creates a strong nudge because the phone is already in hand and the number may be easy to verify. From Google’s point of view, that is a smooth path. From a privacy point of view, it is high-pressure timing.

Android also has backup behaviors that can consume storage. Photos backup, WhatsApp backups, Drive files, and device-related data can all enter the account ecosystem. A 5GB starting point is less forgiving for a phone-first user than for a desktop Gmail-only user.

This is especially relevant in markets where Android dominates as the affordable smartphone platform. The Google Account is not a luxury add-on; it is the key to app installation and device continuity. A storage policy tied to phone-number verification can therefore affect first-time internet users, not only tech-savvy people creating secondary accounts.

A strict reading could say that phone verification is natural during phone setup. The user has a phone, after all. But that assumes the phone number is personal, stable, and safe to attach. It may not be. Some people use shared devices, employer-provided SIMs, prepaid numbers, temporary numbers, or family numbers. Some tablets and Wi-Fi devices have no SIM. Some Android setup flows may be designed specifically for no-SIM contexts.

9to5Google noted that phone verification is required in many account-creation instances but not all, including some cases such as setting up a new Android phone without a SIM card. That variation may be one reason the storage prompt exists: when Google does not require a phone number to create the account, it can still condition the larger storage grant on later verification.

Android onboarding is also where users are least likely to read policy language. They want to finish setup. That raises the burden on Google to make the prompt plain. A user should not discover after the fact that the number has broader settings or that removing it might change recovery.

If the test expands through Android setup, it will feel less like a Gmail policy and more like a mobile identity policy. That could draw more attention from privacy advocates and regulators than a web-only signup experiment.

Google has to balance abuse prevention with accessibility. Phone-number verification may work well in mainstream smartphone use. It may work poorly for users with no stable number, users in regions with SMS reliability issues, or users who need a low-linkage account.

This is where alternative verification could help. Passkeys, device attestation, recovery contacts, payment verification, government ID, email reputation, or trusted-device signals each carry their own privacy and access trade-offs. None is perfect. But offering more than one path reduces the sense that a phone number is the mandatory price of full storage.

Schools, families, and small teams will need clearer rules

Although the test concerns new personal accounts, its ripple effects could reach schools, families, and small teams that rely on informal Google Account setups. Many people create personal Gmail accounts for classroom projects, clubs, volunteer groups, youth sports, side businesses, and shared family tasks. Those uses are common even when a managed Workspace setup would be cleaner.

A 5GB default may not break those accounts, but it makes them harder to use casually. A club email with Drive files, Photos from events, and shared documents can fill 5GB. A school project account may collect videos and slides. A family account may receive scans, backups, and shared albums.

Phone-number verification is awkward for shared accounts because the number usually belongs to one person. That person becomes tied to recovery and storage unlocks. If they leave the group, change numbers, or become unavailable, the account can become fragile. Google generally discourages shared personal accounts for serious organizational use, but real life is messy.

Google Workspace offers managed storage, admin controls, and organizational identity, but it costs money and requires setup. Many small groups do not want that complexity. They use Gmail because it is familiar and free. A conditional storage grant pushes them to think more carefully about account ownership.

Families face similar issues. Parents may create accounts for children before the child has a phone. Grandparents may need help creating accounts and may not understand recovery settings. Siblings may share devices. A phone-number-linked storage unlock can create future recovery confusion if the wrong person’s number is used.

The safest rule for families and small teams is to avoid using one personal Google Account as a long-term shared archive unless ownership and recovery are clear. Use shared folders, family plans, or managed accounts where appropriate. Keep independent backups of irreplaceable photos and documents.

The storage test reinforces that free personal accounts are not neutral infrastructure. They come with account policies, recovery assumptions, and quota rules. A Gmail address can feel like a public utility, but it remains a private platform account with changing terms.

If Google expands the test, it should publish guidance for account types. Personal account, child account, family-managed account, Workspace account, school account, and shared-use scenarios need different advice. Otherwise users will improvise, and many will improvise badly.

The regulatory question is not storage, it is conditional data collection

A company can change free storage tiers. That alone is not usually a regulatory issue. The more interesting question is conditional data collection: can a platform make a larger free allowance depend on providing a phone number, and how clearly must it explain the purpose?

In privacy frameworks, purpose limitation and data minimisation matter. The UK ICO’s explanation of data minimisation says organizations should identify the minimum personal data needed for a purpose and hold no more than that. If Google’s purpose is preventing repeated free storage grants and improving recovery, it can argue that a phone number is relevant. But it must still communicate the purpose and manage downstream uses carefully.

The test is easier to defend if the phone number is truly optional and the user can still create an account with 5GB. It is harder to defend if the account is unusable without a number or if the user cannot understand what uses the number will have.

Regulators may also care about user choice. A choice is less meaningful when refusing creates a material disadvantage. Whether 10GB of storage counts as a material disadvantage will depend on context. For some users, it is minor. For others, it affects email reliability and backups.

Competition authorities may view cloud storage through platform power. Apple has faced legal scrutiny and consumer claims over iCloud storage practices, though the facts differ. The general concern is that operating-system and account ecosystems can steer users into platform storage and paid upgrades. Google’s test is not the same as an iCloud tying claim, but it sits in the same broad policy field: cloud storage inside a dominant consumer ecosystem.

Google can reduce regulatory heat by keeping the 15GB unlock free, explaining phone-number use, and offering alternatives. If the only path to the full allowance is a phone number, and if the account sits at the center of Android access in some markets, the test could draw sharper questions.

There is also a consumer-protection angle. If public pages say “up to 15GB” and signup shows 5GB, the wording is technically consistent. But consumers may have been conditioned by years of “15GB free” messaging. Clear disclosure at signup is therefore essential.

The strongest policy design would be:

• State that some new accounts start with 5GB in the test.
• State that 15GB can be unlocked at no monetary cost by verifying a phone number.
• Explain that the number is used to limit storage grants and support security or recovery.
• Link to phone-number privacy settings.
• Say whether removing the number affects storage.
• Offer another route for users who cannot use a phone number.

A regulator may not require that exact list, but it is the kind of clarity that prevents complaints.

The storage amount is the headline; the legal and trust issue is whether a major platform is using a desirable free feature to collect a stronger personal identifier. That is the question to watch if the test expands.

The economics of free storage have become less forgiving

Free storage once served as a growth engine. It attracted users, encouraged cloud habits, and created lock-in. For Gmail, generous storage helped change email behavior. For Photos, free backup made Google the default memory archive for many people. For Drive, free storage lowered the barrier to cloud documents.

The cost side has never disappeared. Storage hardware, replication, data centers, networking, power, security, reliability engineering, abuse handling, backups, compliance, and support all cost money. At Google’s scale, tiny per-user costs become large aggregate commitments.

The free-tier bargain works when the company gains enough value from engagement, advertising, ecosystem lock-in, paid conversions, device usage, or data signals to justify the subsidy. It becomes strained when storage is abused, users create many low-value accounts, or infrastructure spending rises sharply.

Alphabet remains highly profitable, and Google is not a small company pleading poverty. But profitability does not mean every free grant is strategically rational. Large companies often tighten free tiers precisely because they can measure waste more accurately than before.

A 15GB grant to a real, active user may be worth it. A 15GB grant to a bot account, abandoned account, or duplicated storage account may not be. The phone-number test is a way to separate those categories without charging mainstream users.

This is why the one-per-person language is central. Google is not saying 15GB is too much for a real user. It is saying, in effect, that unlimited repetition of 15GB grants is a problem. That framing lets Google preserve the generous-user story while limiting abuse.

The risk is that ordinary users do not think in infrastructure terms. They think in promises. They remember 15GB. They see 5GB. They feel something was taken away. A technically rational policy can still fail emotionally if it violates a simple expectation.

Cloud storage also has high switching costs. Once photos, email archives, and documents are inside a service, leaving is painful. That gives providers pricing power and policy power. Users know this, which is why free-tier changes provoke strong reactions. A storage downgrade at signup may be less painful than a downgrade after data accumulation, but it still signals what could happen later.

The Google Photos change taught many users that free storage rules can change. The new Gmail-account test reinforces it. People who rely on cloud providers should assume policies will keep evolving. The safest strategy is redundancy: keep local backups, diversify critical archives, and understand export tools.

For Google, the best strategy is to make free-tier evolution predictable. Users can accept limits if they are clear. They resent surprises.

The test could improve account recovery, but recovery is not the whole story

Google’s confirmed statement to Android Authority said the test encourages users to improve account security and data recovery. That is credible. Recovery phone numbers are useful when users forget passwords, lose devices, or face suspicious login challenges. Google’s support page encourages adding a recovery phone number to help regain account access.

Account recovery is not a small issue. A lost Gmail account can mean lost email, photos, files, purchases, app access, YouTube channels, password manager data, and two-factor codes for other services. Strong recovery options matter. Many users only set them after a crisis, when it may be too late.

Using storage as an incentive may therefore have real user benefits. A prompt that says “add a number and unlock 15GB” will likely get more people to add recovery information than a passive security checklist. If that prevents account loss, some users will be grateful later.

But recovery is only part of the story. The reported prompt also says Google will use the number to ensure storage is added only once per person. That is an account-uniqueness purpose, not only a recovery purpose.

The two purposes can coexist, but they should not be blurred. Users deserve to know whether the number is required for their benefit, Google’s resource management, or both. Honest framing builds trust. Overly soft “security” language can sound manipulative if users later realize the number is also enforcing quota limits.

Google has other recovery tools. In 2025, it announced Recovery Contacts, allowing trusted people to help verify identity if a user loses access. Passkeys and device-based sign-in also reduce reliance on passwords and SMS. Those tools show that recovery does not have to depend only on phone numbers.

This raises a fair question: if the real goal is recovery, why not allow the full 15GB after adding a recovery email, passkey, or recovery contact? If the answer is that those do not prevent repeated storage grants, then the goal is not only recovery. It is uniqueness. That is fine, but it should be stated.

Phone numbers are attractive because they do both jobs: recovery and scarcity. Recovery emails can be created endlessly. Passkeys prove device control but may not prove uniqueness. Recovery contacts are helpful but not necessarily anti-abuse signals. Payment methods prove scarcity but would feel even more intrusive for a free account. Government ID would be far more controversial. In that comparison, phone number is the middle option.

Still, users who cannot or will not provide a phone number should not be treated as careless about security. Some may use stronger methods than SMS. They may have passkeys, hardware keys, recovery emails, or careful password practices. A phone-number-centered prompt can make them feel unfairly labeled as less secure.

The best version of the policy would separate recovery strength from storage-grant uniqueness. Google could say: add a phone number to verify storage eligibility; add recovery options to protect your account; review privacy settings for how your number is used. That would be more honest than folding every purpose into a single security message.

Google’s silence beyond the confirmation leaves too many practical gaps

The biggest weakness in the current rollout is not the 5GB number. It is the lack of a detailed public policy page. A confirmed statement to Android Authority establishes that the test is real, but users need operational answers.

The gaps are obvious. Which regions are included? Is the test temporary? Does it apply to all new Google Accounts or only Gmail-created accounts? Does it affect accounts created during Android setup? Are Workspace, school, or child accounts excluded? Can a user unlock 15GB later if they initially keep 5GB? What happens if the phone number is removed? Does the storage drop back to 5GB? How many accounts can one phone number unlock? Are VoIP numbers accepted? Is a recovery email an alternative? Is a passkey enough? Will existing accounts ever be affected?

A company may not want to answer every detail of an abuse-control system. Publishing exact thresholds can help attackers. But consumer-facing policy needs enough clarity for normal users. Google can describe the user impact without disclosing risk-scoring mechanics.

The “select regions” phrase is especially vague. It could mean a small A/B test. It could mean regions with high account abuse. It could mean a staged rollout. It could mean legal or market experiments. Without detail, users outside the test may still worry.

This matters for trust because Gmail is infrastructure for everyday life. Users do not think of it as an experimental product. They expect stable rules. A test affecting storage at signup should be explained with more care than a redesigned button.

The lack of a public Google blog post also invites speculation. Some will tie the change to AI infrastructure costs. Some will tie it to advertising identity. Some will tie it to Google One growth. Some will say it is purely anti-spam. The truth may include parts of several motives, but Google can reduce speculation by being specific about the policy.

The company has done this before. The Google Photos storage-policy change was announced in a blog post months before the June 1, 2021 effective date, with grandfathering details and management tools. Users may not have liked the decision, but the communication was clear.

The Gmail storage test has not had that level of explanation. Perhaps because it is only a test. Yet once screenshots and confirmations are public, the test becomes part of user expectations. Google may have to communicate sooner than planned.

A major account policy should not be understandable only through screenshots and third-party reporting. That is the communications lesson.

A smaller free tier changes the psychology of deletion

Storage management is emotional. People do not delete only data; they delete memories, evidence, work history, receipts, conversations, and records. Gmail’s early genius was reducing the need to delete. The 15GB pool continued that habit for many users. A 5GB default brings deletion back into the foreground.

Google’s help pages give practical steps: empty Trash and Spam, delete large emails, review Drive files, remove backups, and manage Photos. These are useful, but they require judgment. Users have to decide what is safe to remove.

A smaller quota makes those decisions arrive sooner. That can be healthy for people who hoard useless files. It can be stressful for people who keep records for safety, work, or memory. It can be risky for users who delete without understanding what is backed up elsewhere.

The psychological difference between 5GB and 15GB is buffer. A buffer lets users ignore storage while they learn a service. Without it, they face quota management before they have built confidence. That matters for new accounts because early friction can shape long-term habits.

There is also a class effect. Users with money can buy Google One and stop thinking about it. Users without money must manage storage or surrender more identity data to unlock 15GB. A phone number is not money, but it is not nothing. People with stable numbers and low privacy concerns pay less in effort and risk than those without.

This creates a subtle inequality. Free-tier tightening often affects users with fewer resources first. They are less likely to pay, more likely to rely on free accounts, and more likely to be constrained by phone access or shared devices. A policy that seems minor in Silicon Valley can be consequential elsewhere.

The deletion psychology also affects email reliability. When a mailbox is full, incoming messages can bounce. Google’s Drive help page says messages sent to a full Gmail account can go back to the sender. That can mean missed job offers, invoices, appointment notices, verification codes, school messages, or legal communications.

A 5GB new account is more likely to reach that state if used across services without management. The user may not realize Photos or backups caused Gmail failure. Shared quotas make sense technically, but they create blame confusion.

Storage is not just capacity; it is continuity. People need confidence that email will keep working. Any policy that reduces buffer should be paired with clear warnings and easy cleanup.

Google already provides storage management tools. The question is whether they are enough for new users under a smaller default. A cleanup tool helps after the problem appears. The more user-friendly approach is to prevent surprise by explaining what counts early.

The test may push users toward more deliberate cloud habits

There is a constructive side to the news. It reminds users to stop treating a single free cloud account as a permanent archive for everything. Google’s services are reliable, but policies change, accounts can be lost, quotas fill, and recovery can fail.

A deliberate cloud habit has several parts. First, know where critical data lives. Second, keep at least one independent backup of irreplaceable data. Third, maintain recovery options. Fourth, understand what happens when storage is full. Fifth, use paid storage only when the value is clear, not because panic forced a rushed decision.

For Gmail, large attachments are the obvious cleanup target. Google’s help page suggests Gmail search operators for large attachments. Users can also download attachments before deleting messages, though they should preserve important records.

For Drive, sort by storage size and review old files. Shared-with-me files usually belong to someone else, but copies and files added to shared folders can count against your quota. Google’s help page explains that Drive does not have a built-in automatic duplicate finder, so users must review duplicates manually.

For Photos, understand upload dates and quality rules. Photos and videos backed up in High quality or Express quality before June 1, 2021 do not count, according to Google’s storage help page. Newer backups generally do. Deleting older exempt items may not free space, which can confuse users.

For WhatsApp on Android, check whether videos are included in backups. Google’s help page says WhatsApp backups can become one of the largest single storage items and suggests excluding videos to reduce backup size.

For account recovery, add methods that make sense and keep them current. A recovery phone can be useful, but it should be a number the user controls long term. Recovery contacts may help in some cases. Passkeys and two-step verification can strengthen security.

For privacy, review phone-number settings after adding a number. Google lets users manage phone numbers and related preferences. Do not assume a number is used only once and forgotten. Check settings.

The 5GB test may annoy users, but it also makes the hidden storage economy visible. Free cloud storage is not a vault outside business logic. It is a managed service with quotas, incentives, and policies. Users who understand that are less vulnerable to surprises.

Google’s best argument is service quality, not generosity

Google’s strongest public argument is not that 15GB is generous. It is that uncontrolled free storage can harm service quality and account security. The company told Android Authority that the test is meant to help it keep providing a high-quality storage service while encouraging better account security and recovery.

That is a reasonable frame. A platform cannot let abuse consume resources meant for real users. It cannot keep abandoned accounts forever without risk. It cannot make recovery optional and then absorb endless account-loss pain. A large free tier needs guardrails.

The weaker argument would be “nothing changed.” Something did change for users who see 5GB at signup. Denying the practical shift would damage trust. Google’s official “up to 15GB” wording may be technically accurate, but users respond to the experience, not the footnote.

The company should also avoid implying that all users who refuse a phone number are less secure. Some are making a privacy decision. Some cannot use a stable number. Some have better authentication methods. A respectful policy treats them as legitimate users with a smaller storage grant, not as suspicious by default.

The best version of Google’s message would be direct: automatic full storage grants are vulnerable to abuse; phone verification helps limit repeated grants and improves recovery; users who do not want to add a phone number can keep using a smaller free allowance; existing accounts are not affected by the test; privacy controls remain available.

That may not satisfy everyone, but it would sound honest. Users can accept limits more easily than ambiguity.

Google also has to prove the 5GB fallback is usable. If an unverified account constantly nags, breaks core flows, or blocks basic use, the “choice” will feel fake. If 5GB is genuinely usable for light email and Drive, the trade-off is more defensible.

The prompt’s design matters. The option to keep 5GB should not be hidden, shamed, or written in a way that implies the user is making a dangerous choice. The option to add a phone number should state the benefit and data use clearly. Dark-pattern accusations often begin with small wording choices.

Google has the product design capacity to do this well. The question is whether it sees the issue as a trust moment or just an abuse-control test.

The worst-case user fear is retroactive reduction

The fear many users will have is simple: “Will Google cut my existing account to 5GB?” There is no evidence that this is happening under the confirmed test. The reported and confirmed scope is new accounts in select regions. Existing accounts discussed in the reporting still showed 15GB.

That said, users are not wrong to wonder. Platform policies often start with new users and expand later. “Up to 15GB” gives Google flexibility. Google has changed storage rules before. People remember that Google Photos changed from unlimited high-quality backup to quota-counted new uploads after June 1, 2021.

A retroactive reduction would be far more explosive than the current test. It would place existing users over quota instantly if they had more than 5GB stored and no phone number. It could affect Gmail reliability and backups. It would raise fairness concerns. Google would likely avoid that path unless it offered grandfathering, long notice, or a simple unlock.

The more plausible path, if the test expands, is that existing accounts keep 15GB, while new accounts follow the conditional model. Google may also ask existing users without phone numbers to add recovery options, but not cut storage. That is analysis, not confirmed policy.

Google could also maintain region-specific tests indefinitely. Some markets may see 5GB default; others may not. That would create uneven expectations but avoid a single global announcement.

Users who worry about retroactive changes should focus on resilience rather than speculation. Keep storage below quota where possible. Export critical data. Maintain recovery options. Avoid using one free account as the only copy of important files. If paying for Google One, understand what happens if the subscription lapses. Google’s storage help page explains that over-quota status can affect services and, after a long period, deletion eligibility.

The current risk to existing users is not a sudden 5GB cut; the real risk is over-reliance on a cloud policy that can change over time. That risk existed before this test.

The storage test changes the meaning of a new Gmail address

A Gmail address used to come with an unusually clear promise: a strong email service, a Google identity, and a generous storage pool. The new test, where seen, changes the first impression. The address still works. The ecosystem is still powerful. But the account begins with a question: are you willing to attach a phone number?

That question gives the new Gmail address a different symbolic weight. It is no longer only a username. It is part of a verified-person system where storage is allocated based on identity confidence. The user may not think of it that way, but the prompt does.

This fits the direction of the internet. Anonymous or pseudonymous account creation is harder on major platforms. Phone numbers, device fingerprints, passkeys, recovery emails, payment methods, and risk scores all help platforms control abuse. The open web still allows many forms of identity, but large consumer platforms increasingly prefer accounts tied to durable signals.

Gmail is especially important because email addresses are passports to other services. A Gmail account can be used to sign up for banks, marketplaces, social networks, work tools, government services, and recovery flows. Google therefore has strong incentives to keep Gmail account creation from becoming an abuse channel.

But the more Gmail becomes identity infrastructure, the more carefully Google must treat access. A smaller storage grant may sound minor, yet it marks a broader shift from account creation as open access to account creation as graded trust.

The new Gmail address is becoming less of a free container and more of a scored identity. Storage is one visible output of that score.

That does not mean the change is sinister. It means the platform is maturing in a direction that favors verification. Users who value low-friction, low-linkage accounts will feel the loss. Users who value recovery and reliability may see the trade as acceptable.

The story also shows how hard it is to separate consumer benefit from platform control. A phone number can protect an account. It can also help Google limit free grants. It can help users recover access. It can also strengthen identity linkage. It can reduce spam. It can also exclude users with unstable numbers. The same mechanism has multiple consequences.

A mature debate should hold all of those at once. The test is not obviously outrageous. It is not obviously harmless. It is a policy experiment with real trade-offs.

A likely rollout path would be gradual, conditional, and region-aware

If Google expands the test, it is unlikely to flip a single global switch without learning from current data. A more likely path is gradual. The company can test selected regions, measure account creation, phone-number adoption, abuse rates, Google One conversion, support complaints, and churn. It can adjust prompts and thresholds.

This is how large consumer platforms usually handle sensitive changes. A/B tests and regional rollouts reduce risk. They also create confusing public reports because users see different experiences. That is exactly what appears to be happening here.

Google may decide the backlash is not worth the savings and stop. It may decide the test works and expand it. It may keep 5GB only for account flows that lack phone verification. It may require phone verification more often and avoid showing 5GB choices. It may create alternative unlocks. It may preserve the test in high-abuse regions only.

The “up to 15GB” language lets all of those options coexist. It is flexible enough for a global platform. It is also vague enough to frustrate users.

A mature rollout would include a help-page section specifically on storage for new accounts. It would say that storage may vary depending on account verification and region. It would explain how to check quota and unlock more free storage where available. It would clarify that paid Google One plans remain separate.

Google should also monitor whether the policy changes user behavior in harmful ways. Do users skip backups because they keep 5GB? Do they miss email after filling storage? Do they attach phone numbers they later lose? Do they create fewer spam accounts? Do support requests rise? Do users in specific regions face SMS delivery problems?

The company has the data to answer those questions. The public does not. That asymmetry is why transparency matters. Users are asked to trust that the trade-off improves service quality. Google should show enough to make that trust reasonable.

The best evidence that this is a careful anti-abuse policy would be a rollout that is narrow, explained, reversible, and paired with privacy controls. The worst evidence would be a silent expansion that users discover only through quota warnings.

The impact on Google’s brand is larger than the storage saved

Gmail is a trust brand. People may dislike ads, privacy policies, or product changes, but they still rely on Gmail because it works. Storage changes test that trust in a way interface redesigns do not.

A 5GB default can be framed as reasonable. It aligns Google more closely with Apple and Microsoft if the phone number is not added. It keeps the full 15GB free for verified users. It helps prevent storage abuse. It improves recovery. These are serious points.

But users compare products to promises, not only competitors. Google’s promise was 15GB for so long that “up to 15GB” feels like a retreat. The company may save storage exposure, but it spends brand goodwill.

Brand goodwill is hard to measure. It appears in whether users recommend Gmail, whether they accept new prompts, whether they trust Google Photos with memories, whether they buy Google One without resentment, and whether they believe future policy changes will be fair.

Google’s challenge is that it is already under scrutiny for AI changes, advertising, privacy, antitrust, and ecosystem power. A storage test can become a symbol of larger complaints: Google gives less, asks for more data, and nudges users into subscriptions. That narrative may be too simple, but it is potent.

The company can counter it only with clarity. “We are testing in select regions” is a start. It is not enough. Users need to know whether the old account promise still holds for them and what exactly the new-account promise is.

The brand risk is not that users cannot survive on 5GB. The brand risk is that Gmail’s once-simple bargain now feels conditional and opaque.

If Google handles this well, most people will move on. They will add phone numbers, keep 15GB, or buy storage. If it handles it poorly, the story will become another data point in a long-running perception that free consumer tech services are slowly tightening around users after they become dependent.

The answer for new users is practical, not ideological

A person creating a new Google Account today should make a practical decision. If the signup flow offers 5GB by default and 15GB after phone-number verification, decide whether the extra storage and recovery benefits are worth adding the number.

For many users, the answer will be yes. A stable personal mobile number can help account recovery, and the extra 10GB gives more breathing room across Gmail, Drive, and Photos. After adding the number, the user should review phone-number settings and privacy preferences.

For users who do not want to add a phone number, 5GB can still work for a light account. Keep Photos backup off, avoid using the account as a Drive archive, delete large attachments when no longer needed, and maintain local copies of important files. Do not use the account for large WhatsApp backups.

For users who need more storage but do not want phone-number linkage, paid options or alternative providers may be cleaner. Google One adds storage but still sits inside the Google Account ecosystem. Other providers have their own trade-offs in price, privacy, storage size, and convenience.

The worst decision is to ignore quota until Gmail stops receiving mail. Google’s support pages make clear that a full account can affect Gmail, Drive, and Photos. Storage should be checked before it becomes urgent.

For parents, small teams, and shared-use accounts, plan ownership before adding a phone number. The number should belong to the person who will manage recovery long term. If no such person exists, a managed Workspace or family setup may be safer than a shared personal account.

For journalists, activists, or vulnerable users, treat phone-number linkage as a threat-model decision. Storage is useful, but account separation may matter more. A smaller quota may be acceptable if it preserves safety.

The right answer depends on the account’s purpose. A main personal account, a throwaway signup account, a child’s account, and a sensitive work account should not be treated the same.

The broader lesson is that free tiers are becoming trust filters

The Gmail storage test is part of a larger pattern across consumer technology: free tiers are no longer only acquisition funnels. They are trust filters. Platforms use limits, verification, device signals, usage caps, and feature gates to sort users by risk, value, and commitment.

That shift is not always bad. It can reduce spam, fraud, abuse, and waste. It can keep services usable. It can protect real users from bad actors. But it also makes access less equal and less anonymous. The user pays with money, data, friction, or reduced capability.

In this case, the currency is a phone number. The reward is the familiar 15GB storage allowance. The fallback is 5GB. That is a clean product mechanic, and that is why it is so revealing.

Google’s challenge is to avoid turning a trust filter into a trust problem. If users believe the phone number is necessary, limited in use, and beneficial, the test may pass. If they believe it is a stealth data grab or subscription funnel, it will damage goodwill.

The difference will be made by details: wording, settings, reversibility, alternatives, public documentation, and whether existing users remain protected.

Free storage was once a promise of abundance. It is now becoming a promise with conditions. Gmail is only the latest and most visible place where that shift has surfaced.

The most likely near-term outcome is confusion before clarity

For now, the public facts are limited. Google has confirmed a test for new accounts in select regions. Some signup flows reportedly show 5GB by default and a phone-number unlock for 15GB. Google’s official storage pages say “up to 15GB.” Existing accounts have not been publicly cut under this test. That is the current state.

The next phase will likely bring more user reports. Some people will see the prompt; others will not. Some will create accounts through Android; others through desktop. Some regions may be included; others excluded. Tech sites will test flows. Support forums will fill with conflicting claims.

Google can shorten that confusion by publishing a clear help page. Until then, the best answer will remain conditional.

The company may also update wording again. If the test expands, “up to 15GB” may become the permanent phrasing. If it ends, Google may still keep the phrase because it offers flexibility. Users should not expect the old wording to return quickly.

For Google, the decision will be data-led. If the test reduces abuse and increases recovery setup without hurting account creation or trust metrics too much, expansion is plausible. If it creates backlash or support problems, the company may alter it.

For users, the path is simpler: check quota, understand what counts, keep backups, and make an informed choice about phone-number linking.

The story is still developing, but the direction is clear enough. Google is testing whether the full free storage grant should belong to a more verified account, not just any new account. That is a meaningful change to the Gmail-era bargain.

Questions and answers about Google’s 5GB Gmail storage test

Author:
Jan Bielik
CEO & Founder of Webiano Digital & Marketing Agency

This article is an original analysis supported by the sources cited below

The era of 15GB free Gmail storage is ending
Android Authority report updated with Google’s confirmation that it is testing a 5GB storage limit for some new Gmail users unless they add a phone number.

Google accounts no longer get 15GB of free storage, only 5GB until you link a phone number
9to5Google report documenting the new-account storage prompt and the shift in Google’s public wording toward “up to 15GB.”

Google may be quietly testing a controversial Gmail change
Android Police coverage of user reports and the apparent 5GB default for some new Google accounts.

Only 5GB default free storage for new Gmail accounts with no phone number
PiunikaWeb report tracking early user sightings of the 5GB storage prompt.

How your Google storage works
Google One Help page explaining that Google Account storage is shared across Gmail, Google Drive, and Google Photos and describing over-quota effects.

Manage your storage in Drive, Gmail and Photos
Google Drive Help page describing shared storage, Gmail send/receive effects, cleanup steps, large attachment searches, and WhatsApp backup storage.

Plans and pricing to upgrade your cloud storage
Google One plan page showing the “up to 15GB” free storage language and paid storage tiers.

Bringing it all together 15GB now shared between Drive, Gmail, and Google+ Photos
Official Gmail Blog post from 2013 announcing the unified 15GB free storage pool across Gmail, Drive, and Google+ Photos.

Updating Google Photos’ storage policy to build for the future
Google announcement explaining the end of unlimited High quality Google Photos uploads for new backups after June 1, 2021.

4 things to know about Google Photos’ storage policy change
Google Photos update before the June 1, 2021 policy change, explaining how new uploads would count toward account storage.

An update to storage policies across your Google Account
Google blog post explaining storage policy changes, inactivity rules, over-quota handling, and the 15GB shared storage model.

Verify your account
Google Account Help page explaining that Google limits how many accounts each phone number can create to protect against abuse.

Add your phone number
Google Account Help page explaining recovery phone-number use for regaining access to an account.

Change the phone number on your account and how it’s used
Google Account Help page describing how users can manage phone numbers and related preferences.

Google Privacy Policy
Google’s privacy policy covering personal information and account data controls.

Inactive Google Account Policy
Google Account Help page explaining that personal Google Accounts may be deleted after at least two years of inactivity.

Updating our inactive account policies
Google announcement explaining the 2023 inactive-account policy update and its security rationale.

Add trusted contacts for Google account recovery
Google announcement of Recovery Contacts as an account recovery option.

Alphabet Investor Relations 2026 Q1 earnings call
Alphabet investor page with Q1 2026 capital expenditure details and technical infrastructure spending commentary.

Alphabet Q1 2026 earnings remarks
Google blog post with Sundar Pichai’s Q1 2026 remarks on Google Cloud revenue growth, AI demand, and cloud backlog.

Alphabet announces first quarter 2026 results
SEC-hosted Alphabet Q1 2026 earnings release with revenue, operating income, and Google Cloud performance.

iCloud+ plans and pricing
Apple Support page stating that iCloud includes 5GB of free storage and listing iCloud+ upgrade options.

Free cloud storage for photos and files with OneDrive
Microsoft OneDrive page showing 5GB of free cloud storage in the free consumer offer.

What is Dropbox Basic
Dropbox Help page explaining that Dropbox Basic is a free plan with 2GB of storage.

Unlock more free storage for your new Proton Drive account
Proton support page explaining how new free Proton Drive users can unlock extra storage through welcome actions.

Principle c data minimisation
UK Information Commissioner’s Office guidance explaining the data minimisation principle and its relevance to personal data collection.