Urgent.News

What's breaking now, across thousands of outlets.

Tech

I tested the AirPods 5 vs the AirPods 4 ANC — should you upgrade?

What are the differences between the AirPods 4 ANC and the brand-new AirPods 5? Are the AirPods 5 worth the upgrade?

I tested the AirPods 5 vs the AirPods 4 ANC — should you upgrade?

Two years after the AirPods 4 ANC launched, Apple has released the AirPods 5, which are even more affordable. At prices starting at $124, these earbuds are the cheapest AirPods ever released. Notably, the AirPods 5 come with Active Noise Cancellation (ANC) as standard, whereas the AirPods 4 ANC required an additional $50 for ANC. Although there's a slight difference in battery life between the $124 standard charging case model and the $149 wireless charging case model, this isn't significant.

However, the question remains: should you upgrade from the AirPods 4 ANC to the AirPods 5? I'll compare the two models to help you decide.

The AirPods 5 are significantly cheaper than their predecessor, starting at $124 compared to the $149 price of the AirPods 4 ANC. They also feature ANC as standard and Apple's powerful H2 chip, which enables integrated Siri AI features. While the AirPods 4 ANC are still available for $149, the AirPods 5 offer better value for money.

Both models boast similar connectivity, with Bluetooth 5.3. The AirPods 5 have a longer battery life, offering 5 hours (ANC), 20-32 hours (ANC) with the wireless charging case, and 4 hours (No ANC), 30 hours (ANC) with the standard charging case. The AirPods 4 ANC, on the other hand, provide 4-5 hours (ANC) and 20-32 hours (ANC) with the standard case.

In terms of durability, the AirPods 5 now match the AirPods Pro 3 with an IP57 rating, making them capable of surviving underwater for half an hour. Furthermore, the AirPods 5 have added volume swipe control, an upgrade that's welcomed compared to the slightly smaller AirPods 4 ANC and wireless charging case.

Written by urgent.news from Tom's Guide's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at tomsguide.com →

More in Tech

The secret was correct. The first byte wasn't.

Our deploy tool pushed a fresh API token to production. It reported success. The token was correct. Every request then failed with this: Cannot convert argument to a ByteString because the character…

Point the official Sentry SDK at self-hosted ingest (DSN only)

You don’t need a forked Sentry SDK. Keep @sentry/browser or @sentry/node , change only dsn , then prove /health → HTTP 202 → Issues.

  • Clone the public repo and run Docker Compose to set up self-hosted ingest.
  • Install pinned official Sentry SDK (7.120.0) with custom DSN and settings.
  • Verify SDK ingestion by capturing an exception and checking for 202 response.

More from Sunday 20 September →