Why This Experiment Even Matters in 2026
Storage has become surprisingly expensive. With AI tools becoming mainstream and cloud providers continuously pushing premium plans, local storage solutions are no longer cheap. Even SSD prices have gone up significantly. Building large-scale storage systems today can cost a fortune. In our case, we have a NAS setup with roughly 40TB of storage, and replicating a similar setup in 2026 would cost an absurd amount of money. That got me thinking. What if I simply uploaded everything to Google Photos through the original Pixel? Would Google still allow unlimited uploads? More importantly, would Google eventually ban the account if I abused the feature by uploading terabytes of data? There was only one way to find out.
The First Problem: It's Not as Simple as It Sounds
Initially, I thought the process would be straightforward. I could simply sign into the same Google account on the Pixel, transfer files from my laptop, upload them, and call it a day. Unfortunately, Google had other plans. I tested this by taking a photo on my current smartphone, transferring it to my laptop, and then uploading it manually to Google Photos using the same Google account. The result? The storage usage immediately increased. That meant manually uploading files from a computer would still count against my storage quota. Google has also become stricter with storage limits over the years. New accounts currently receive limited storage initially, and additional steps are required just to unlock the standard quota. So clearly, there was a catch. For unlimited backups to work, the media needed to originate from the Pixel itself or at least appear inside its camera folder before uploading. To verify this, I transferred a photo to the Pixel, placed it inside the camera folder, and uploaded it directly from the device. It worked. The storage usage remained unchanged. Unlimited storage was still alive.
Time for the Big Test
Encouraged by the results, I moved to the real challenge. I copied a large video file from our NAS onto the Pixel and waited. The upload completed successfully. When I checked Google storage usage, it still showed virtually no consumption. At this point, I was excited. The loophole still existed. But there was an enormous practical problem. The original Pixel I purchased came with just 32GB of storage. Meanwhile, I wanted to upload around 40TB. Doing this manually would require an insane number of transfer cycles. Considering the phone's age and performance limitations, this process could realistically take years. Clearly, manually copying files wasn't an option. I needed automation.
Searching for a Smarter Solution
My first idea involved using an app called Resilio Sync. The concept was brilliant on paper. I could install the app on both my primary smartphone and the Pixel. Every photo and video would automatically sync to the Pixel, get placed inside the camera folder, and then Google Photos would upload everything for free. Problem solved. Or so I thought. Unfortunately, things didn't go according to plan. While Resilio Sync supports laptops and NAS systems, our particular NAS setup wasn't cooperative. Recent firmware updates had made it increasingly unfriendly toward third-party applications, and Resilio Sync kept breaking repeatedly. The solution that looked perfect simply wasn't reliable for our setup. Back to square one.
When in Doubt, Start Coding
At this point, I decided to take the more difficult route. We wrote our own solution. Well, technically, we asked an AI assistant to generate the first version of the script. On paper, it seemed incredibly simple. Copy files. Upload files. Delete files. Repeat. Easy, right? Not exactly. When we ran the script for the first time, absolutely nothing happened. No output. No progress. Nothing. The real issue turned out to be our NAS structure. Over the years, it had become a complete mess with folders nested inside folders inside even more folders. The script simply couldn't navigate through everything properly. After modifying the code to scan deeper directory structures, things finally started working. Files began transferring successfully. For a brief moment, I thought we had cracked it. Then the phone started melting.
The Pixel 1 Became a Portable Heater
I knew the original Pixel was old. What I didn't expect was just how poorly it would handle continuous data transfers. Pushing gigabytes, and eventually terabytes, through a decade-old smartphone turned it into a miniature oven. The device became incredibly hot. At one point, the temperature increased so much that uploads simply stopped. The battery situation was even worse. Despite being connected continuously, the phone occasionally shut itself down due to heat and battery degradation. On one occasion, we only discovered the shutdown the next morning. Even with a perfectly functioning script, the hardware itself had become the bottleneck. So we improvised.
Turning a Smartphone Into a Server
Since the battery couldn't survive on its own, I kept the Pixel connected to power 24/7. That introduced another issue. Charging generated additional heat. More heat meant more failures. So we did what any reasonable tech enthusiast would do. We attached a gaming phone cooler to the back of the Pixel. Suddenly, this wasn't a smartphone anymore. It had officially become a server. We also improved the automation significantly. After every upload cycle, the script would pause and allow the device to cool down before continuing. Storage would then be cleared and the next batch would begin. We even introduced thermal safeguards. If the phone temperature crossed 40 degrees Celsius, uploads would automatically pause. Google Photos also presented another challenge because it never explicitly confirmed when uploads had completed. To solve this, we tracked network activity. Whenever transfer speeds dropped significantly, we assumed the upload had finished and moved on to the next batch. It was messy. But it worked.
Day 45: The First Major Roadblock
Around one and a half months into the experiment, another issue surfaced. Certain video files simply refused to upload. Google Photos didn't even provide a manual backup option for those files. Instead, they appeared with a "device only" label. No matter what I tried, I couldn't identify a concrete reason. Some videos uploaded flawlessly. Others were ignored completely. Despite this strange limitation, the vast majority of photos and videos uploaded successfully. Most importantly, everything was uploaded in original, uncompressed quality. Even after uploading huge amounts of media, storage usage remained almost unchanged. Unlimited storage was still working.
Day 100: The Internet Provider Fought Back
The second major obstacle wasn't Google. It was our internet connection. I had assumed our office fiber connection offered truly unlimited data. Turns out, it didn't. After transferring massive amounts of data for months, our internet provider eventually enforced its Fair Usage Policy. Essentially, while the connection is marketed as unlimited, extremely heavy usage triggers speed restrictions to ensure fair bandwidth distribution among all users. Once we crossed the limit, our blazing-fast internet slowed down dramatically. Uploads that previously took minutes suddenly became painfully slow. At that point, the experiment effectively stalled.
So, Did We Succeed?
Not completely. We failed to upload the entire 40TB dataset. However, we still managed to upload approximately 8TB of data over three months. More importantly, Google never banned our account. That was probably the biggest surprise of the entire experiment.
Should You Buy a Pixel 1 for Unlimited Storage?
After spending more than 100 days experimenting with this setup, my answer is surprisingly simple. Yes, it can make sense. If your goal is purely affordable long-term media backup, spending ₹5,000 to ₹6,000 on an original Pixel could still be cheaper than purchasing large amounts of cloud storage. That said, I would strongly recommend not using your primary Google account for experiments like this. If Google ever decides to suspend the account for suspicious activity, losing access to your primary email would be disastrous. I used a separate account specifically for this purpose. I also recommend linking that account as a partner account to your primary account so you can continue accessing all backed-up media conveniently.
Final Thoughts
This turned out to be one of the most interesting tech experiments I have done in a long time. The original Pixel may be nearly a decade old, but it still holds one incredibly unique advantage that modern smartphones simply don't offer. The experiment wasn't perfect. We didn't upload all 40TB. The phone overheated constantly. Internet limitations slowed us down. Several files refused to upload. Yet despite all these problems, the core idea worked. And honestly, that's what made this experiment so fascinating. One final thing: while the experiment itself ran for over 100 days, much of the video production was completed within a few days. I wanted to keep that transparent because being honest about how these experiments are presented is important. In the end, a 10-year-old smartphone still managed to surprise me in 2026. And I definitely didn't expect that.
This article is completely written with the help of the videos of big tech reviewers on YouTube. This device is tested and the opinions are completely from the tech reviewer.
.jpg)
0 Comments