Google’s new Noto 3D emoji require Android 17, 6 GB of RAM and 10 GB of free storage, specs that exclude most budget phones and all Samsung Galaxy devices, Android Headlines reported.
The requirements appeared on a Google support page, explaining why the rollout has reached only the Pixel 11 line and some older Pixels since the May announcement. Noto 3D emoji swap the old vector glyphs for a high-resolution bitmap font, trading infinite scalability for pre-rendered texture and depth.
TheVerge noted that Google’s Mishaal Rahman later clarified the numbers: the font itself occupies roughly 220 MB, but Play Services needs temporary headroom to stage the download, and the 6 GB RAM threshold is a deliberate cutoff to keep low-memory devices on the 3 MB vector set.
“Android doesn’t load the 3D emoji font file into RAM,” Google wrote on Reddit, adding that usage is “minimal & transient” during the background install. 9to5Google reported the same explanation, noting that eligible devices pull the update automatically only while on Wi-Fi and charging, with no manual trigger available.

The switch to bitmap graphics introduces a regression vector emoji never had. Google’s own FAQ warns that the new glyphs can look blurry when apps enlarge them or users zoom in, because pixel-based assets stretch instead of recalculating curves.
Samsung devices are explicitly excluded. The support page states Galaxy phones “use a proprietary emoji font and do not receive the 3D font update.” That lock-in extends to third-party messengers: WhatsApp and similar apps bundle their own emoji sets, so even Pixel owners will see the old 2D styles inside those conversations.
The Verge and Android Police both confirmed Samsung devices will not receive the 3D emoji, highlighting how OEM font forks fragment the Android emoji baseline.
| Requirement | Threshold | Rationale (per Google) |
|---|---|---|
| OS version | Android 17+ | Platform API support for bitmap font delivery |
| RAM | 6 GB minimum | Cutoff to keep low-memory devices on 2D vector font |
| Total storage | 128 GB | Ensures headroom for staged download via Play Services |
| Free space | 10 GB | Temporary cache for copy-into-place operation |
The 10 GB free-space rule does not reflect the font’s final footprint. 9to5Google detailed the install choreography: Play Services downloads the ~220 MB bitmap, copies it into the system font directory, then purges the cache. Devices that shipped with the 3D font pre-installed — Pixel 11 series — bypass the entire flow.
Google’s decision to deliver the feature via Play Services updates rather than a full OS upgrade speeds delivery for supported OEMs, but the RAM and storage floors create a new tier of “emoji haves” within Android 17 itself. Budget handsets selling in 2026 with 4 GB RAM and 64 GB storage — still common in emerging markets — will never see the update, even if they meet the version requirement.

Google has not published a public API to detect 3D font presence at runtime.
The rollout continues this week for eligible non-Pixel Android 17 devices. Google’s support page promises no manual download button and no timeline for expanding the supported manufacturer list beyond the current cohort.
Worth a look
- Knee Surgery Journal: J Knee Surg Facts – CASRAI
- LG Display’s FLiPP OLED Tech Targets 2030 MacBook Air and iMac
- Google Says It Removed 19,372 Pro-Govt YouTube Channels in Indonesia for Coordinated Influence Ops (world-today-news.com)
- How Google Traced GKE API Timeouts to a Linux Kernel TCP Bug (newsy-today.com)