What you need to know
- Apple may finally offer the iPhone in a 1TB configuration.
- Apple leaker Jon Prosser posted about the possibility on Twitter.
- It is unclear if Apple will add the storage option to its existing lineup or wait until next year.
Reported by Apple leaker Jon Prosser, Apple is planning to bring 1TB of storage to the iPhone for the first time. Prosser posted a relatively simple and, as leaks usually go, vague tweet about the subject.
Prosser did not offer details as to what iPhone would be the first to feature 1TB of storage. The leaker could mean that Apple may begin to offer its new iPhone 12 lineup in an additional 1TB configuration, but that is unlikely as Apple would probably have had that storage size ready for the phone's launch.
What is more likely is that Apple plans to offer its next lineup of iPhones in a 1TB configuration. The iPhone 12 is currently offered in 64GB, 128GB, and 256GB, whereas the iPhone 12 Pro is offered in 128GB, 256GB, and 512GB. It is unclear if 1TB will be added as a fourth option or if it will replace one of the existing options.
Regardless, those who regularly max out the storage offering of their iPhones will be happy to hear of the news.
Joe Wituschek is a Contributor at iMore. With over ten years in the technology industry, one of them being at Apple, Joe now covers the company for the website. In addition to covering breaking news, Joe also writes editorials and reviews for a range of products. He fell in love with Apple products when he got an iPod nano for Christmas almost twenty years ago. Despite being considered a "heavy" user, he has always preferred the consumer-focused products like the MacBook Air, iPad mini, and iPhone 13 mini. He will fight to the death to keep a mini iPhone in the lineup. In his free time, Joe enjoys video games, movies, photography, running, and basically everything outdoors.
Get the best of iMore in in your inbox, every day!
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.