A used Pixel 6 is at the end of Google's update window

A Pixel 6 or Pixel 6 Pro bought in October 2026 is collecting the last weeks of a five-year promise. It is not entering the seven-year window Google advertises on newer Pixels.

Google's support page divides the phones. Pixel 8 and later models get seven years of operating-system updates and security patches, counted from the month the device first went on sale in the US Google Store. Those years can also include feature drops. The Pixel 6, Pixel 6 Pro, Pixel 6a, the Pixel 7 phones and the original Pixel Fold get five years on that same clock. Pixel 5a and every older Pixel are already finished for both version updates and security updates.

Google's availability table supplies the start dates. Pixel 6 and Pixel 6 Pro became available in October 2021, so five years lands in October 2026. Pixel 6a is dated July 2022, which runs to July 2027. Pixel 7 and Pixel 7 Pro are October 2022, through October 2027. Pixel 7a is May 2023, through May 2028. The original Pixel Fold is June 2023. Engadget's Max Miller, on 11 October, walks that same arithmetic and names the Pixel 6 and 6 Pro as the pair reaching the end of support this month. Beebom's guide, published 13 October, describes the same seven-year rule for operating-system and security updates on Pixel 8 and later, and it notes that feature drops sit inside that window. The start date itself is Google's. It is the US store month, not the day a second owner pays.

The Pixel 8 shows why the model number is the whole decision. Google dates the Pixel 8 and Pixel 8 Pro to October 2023. Seven years from that month is October 2030, which is the reading Engadget publishes. A used Pixel 8 and a used Pixel 6 can sit in the same shop window. Only one of them still has a multi-year patch commitment. Google's clock is the US store month, so a handset that reached another country later does not pick up extra years. A regional variant this page does not name is a reason to stop and check the exact model, not a reason to assume the US date is wrong in your favour.

The error that costs money is reading the security-patch date in system settings as an expiry date. Engadget's 6 October guide draws the line. That date is when the phone last received a fix. It is not a statement that another fix is scheduled. Engadget's rule of thumb is that a patch more than three to six months old is a sign the phone may be near the cutoff or already past it. It is a warning. The cutoff is the policy plus the first-sale month. Paying for the phone last week does not move either.

There is a second trap inside one family. The Pixel 6 and the Pixel 6a do not end together. October 2026 and July 2027 are nine months apart, and a listing that says Pixel 6 series is not a specification. Match the model, then add the years Google actually promised that model.

Engadget's 11 October piece is direct about the usual workaround. A custom system such as LineageOS can keep delivering some framework and kernel patches after Google stops, and those patches do not include the phone maker's firmware, kernel and vendor code. On an unlocked bootloader, Engadget writes, apps that require verified boot stop cooperating. Banking apps, wallet apps and games with anti-cheat are the examples it gives. Keeping a Pixel 6 past this month means living with flaws Google will not patch, or living with that breakage. It does not restore the update the phone was sold with.

Samsung runs its own list. Engadget's checking guide says the Galaxy S24 line and the Fold and Flip 6 generation are on seven years, while older Galaxy A phones and flagships from 2019 are generally on four, with some budget models on six, again from first sale. A single letter in a Galaxy model code can put a phone on another row. The move before paying is the same one. Take the exact model, find the month it first went on sale, add only the years that model was promised, and do not pay a supported-phone price for a Pixel 6 or Pixel 6 Pro in the month that window closes.