Email Tracking Pixels: How They Work and How to Block Them (2026 Guide)

The next time a newsletter, a marketing email, or a sales pitch lands in your inbox, look closely. Somewhere in that message, often near the footer, there is a one-pixel transparent image that you cannot see. The moment your mail client loads it, a server somewhere logs the request. Time of open, your approximate location, your device, your mail client. Sometimes more.

This is a tracking pixel. According to research from DuckDuckGo, roughly 85% of the emails that pass through privacy-focused inboxes contain at least one. They are the silent default of modern email.

This guide explains how tracking pixels work, what they reveal about you, and what actually blocks them in 2026.

How a Tracking Pixel Actually Works

The mechanism is simpler than it sounds.

An HTML email is a small web page. It can contain text, formatting, links, and images. When your mail client renders the message, it has to fetch each image from wherever the sender hosted it. That fetch is a normal HTTP request to a server, and like every HTTP request, it leaves a log entry.

A tracking pixel is just an image with three properties:

• It is 1×1 pixel in size, so you cannot see it.
• Its URL is unique to you. Something like https://track.example.com/p/3f8c2a9e1b.gif, where the long string encodes your email address or campaign ID.
• It is hosted on a server the sender controls or pays for.

The moment your mail client loads the image, the sender’s server logs:

• That this specific recipient (you) opened the email.
• The exact timestamp.
• Your IP address, which usually resolves to a city.
• Your User-Agent string, which reveals your mail client, browser, and operating system.
• Whether you have opened it before, and how many times.

If you forward that email, the pixel fires again every time someone else opens it. The sender now knows their message was shared, and roughly where.

What They Reveal in Practice

Tracking pixels do not give the sender a screen recording of your inbox. What they give is a steady stream of small data points that, in aggregate, paint a precise picture.

For a marketing team, that picture looks like this:

• Which subject lines you actually open.
• What time of day you read email (and therefore the best time to send you the next one).
• Whether you read on mobile or desktop, on iOS or Android, on Gmail or Outlook.
• Roughly where you live, and whether you read at home or at the office.
• Whether you opened the email once, ignored it, then opened it again three days later, which is a strong buy signal in B2B sales tools.
• How many times each link was clicked (more on that in a moment).

For individuals using tools like Mailtrack, Streak, HubSpot Sales, or Mixmax, the same pixel reveals whether their cold pitch was opened, whether the recipient is currently re-reading it, and whether it has been forwarded.

None of this is illegal in most jurisdictions. None of it requires explicit consent under most readings of GDPR, although a strict reading suggests it probably should. It happens by default, in almost every commercial email you receive.

How to Detect a Pixel Yourself

If you want to see one in the wild, open any marketing email and view the message source.

• Gmail (web): click the three dots, choose “Show original”.
• Apple Mail: View → Message → Raw Source (⌥⌘U).
• Outlook (web): three dots → “View” → “View message source”.
• Thunderbird: View → Message Source (Ctrl+U).

Search the source for <img. The pixels are usually obvious once you know what to look for. Hallmarks include:

• Width and height set to 1 (width="1" height="1").
• display:none or visibility:hidden in the inline style.
• A src URL pointing to a domain like track., open., mailtrack.io, hubspot.com, mailgun.org, or a long random string.
• A URL parameter that encodes your email address or a long hash.

Open the Marketing tab in any commercial inbox, pick three messages at random, and check. The hit rate is usually higher than 80%.

What Actually Blocks Them

There are five effective approaches, and each has trade-offs.

1. Block remote images by default

This is the most reliable defense. If your mail client never loads images automatically, the pixel never fires. Every major mail client has this setting:

• Gmail (web): Settings → General → “Ask before displaying external images”.
• Apple Mail: Settings → Privacy → uncheck “Load remote content in messages” (this is separate from MPP and works without it).
• Outlook (web and desktop): Settings → Mail → External images → “Always ask before downloading”.
• Thunderbird: Settings → Privacy & Security → uncheck “Allow remote content in messages”.
• YouniqMail: remote images are off by default, with a per-sender allow option.

The cost is that legitimate images break too. Newsletters look stripped down. Product photos in transactional emails are missing. You will see a row of empty placeholders with a “Load images” button at the top, and you click it when you actually want to see the content.

Most people who try this for two weeks never turn it back on. The inbox becomes faster, lighter, and more text-focused.

2. Apple Mail Privacy Protection

Apple’s Mail Privacy Protection, or MPP, was introduced in 2021 and is now used by roughly half of all Apple Mail accounts. It works differently from anything else on this list.

Instead of blocking the pixel, MPP fires it deliberately. The moment an email arrives in an Apple Mail inbox, Apple’s servers pre-load the entire message, including every image, including the tracking pixel. Then Apple delivers the cached content to your device through two separate relays operated by different entities, so no single party can link your IP address to the content you received.

The effect for the sender is twofold. First, the pixel reports an “open” for every message, whether the recipient actually read it or not. Second, the IP address in the log is Apple’s proxy, not yours.

For the user, this is a real privacy win. For the sender, open rates from Apple Mail recipients are now effectively meaningless, which is why most marketing analytics platforms label them as “machine opens” and exclude them from real engagement calculations.

MPP applies to any email account accessed through the Apple Mail app, including Gmail, Outlook, and Yahoo addresses. It does not apply if you access the same accounts through the Gmail or Outlook apps.

3. Gmail’s image proxy

Since 2013, Gmail has automatically routed all images in emails through Google’s own proxy servers. This means the tracking pixel does fire, but the sender’s log records a Google IP, not yours. The sender still knows the email was opened but cannot geolocate you or fingerprint your network.

This is partial protection. Time of open is still tracked. Repeat opens are still tracked. Device is still partially tracked through the User-Agent in the proxy request. But the location leak is plugged.

4. Browser extensions

For Gmail, Outlook web, and Yahoo Mail, several extensions block pixels at the browser level before they load.

• Trocker. Open source, works across most webmail services (Gmail, Outlook.com, Yahoo, ProtonMail web), and includes link-tracking protection. Runs locally with no data leaving your machine.
• PixelBlock. Gmail only, but well-maintained and consistently rated highly. Displays a red eye icon next to senders who tried to track you.
• Ugly Email. Takes a different approach: it does not block pixels, it warns you with an eye icon in the inbox list before you open the message, so you can decide whether to open it at all.

Note for Chrome users: Google’s Manifest V3 update in early 2025 broke or limited many privacy extensions. Verify that the extension you choose has been updated for Manifest V3, or use Firefox, which kept the older extension architecture.

5. DuckDuckGo Email Protection

DuckDuckGo offers free @duck.com addresses that act as forwarding aliases. Email sent to your duck.com address is stripped of trackers before being forwarded to your real inbox. Their public data is the source of the 85% tracker prevalence statistic.

This is useful for newsletter sign-ups, accounts you do not fully trust, and any time you want to give out an email address without exposing your primary one.

The Link Tracking Problem

Even with every pixel blocked, the email you just received probably still tracks you through its links.

The links in marketing emails almost never point directly to their destination. They route through a tracking domain first. A link that looks like it goes to example.com/article actually goes through click.sender-marketing.com/abc123/redirect, which logs the click and then redirects you. The sender knows you clicked, which link you clicked, and (via the redirect) often your IP and User-Agent at the moment of the click.

Two defenses against this in 2026:

• Apple’s Link Tracking Protection (introduced in iOS 17 and expanded in iOS 18) automatically strips known tracking parameters like utm_source, fbclid, and mc_cid from links opened in Mail and Safari Private Browsing.
• Browser extensions like ClearURLs and uBlock Origin do the same on the desktop, across any browser and any link source.

Neither blocks the click-through redirect itself, but both prevent the tracking parameters from following you to the destination page.

Is Any of This Worth Doing?

It depends on what you care about.

If your only concern is that companies know roughly when you read their newsletters, the answer is probably no. The information is mundane and the trade-off (broken images, missing newsletter visuals) costs you something every day.

If you care about the cumulative picture, it matters more. A single open event is harmless. Tens of thousands of open events across hundreds of senders over years build a remarkably detailed profile of your habits, your devices, your locations, and your relationships. That profile is almost always sold, shared, or breached eventually.

If you do sensitive work (journalism, legal, medical, activism), the answer is yes, and you should also be thinking about which mail client and provider you use, not just which extensions you install. Local-first mail clients with images off by default give you a substantially smaller attack surface than browser-based webmail with everything enabled.

FAQ

Are tracking pixels legal?

In most jurisdictions, yes. GDPR’s stance is contested: some regulators consider tracking pixels equivalent to cookies and therefore subject to consent requirements, others do not enforce that interpretation. CCPA, CPRA, and similar US state laws have not directly addressed them. In practice, almost every commercial email you receive contains at least one, and enforcement is rare.

If I block tracking pixels, will senders know?

They will know in the sense that no “open” event will be recorded for you. They will not know specifically that you blocked the pixel versus simply never opening the email. To the sender’s analytics, you look like a recipient who deletes their emails unread.

Does an end-to-end encrypted email service block tracking pixels?

Not by default. Encryption protects the content of messages you send, not the images embedded in messages you receive. ProtonMail and Tuta do strip some tracking pixels through additional features, but enabling image loading still allows many to fire.

Why does Apple Mail report 100% open rates to my newsletter?

Because of Mail Privacy Protection. Apple pre-loads every email and fires every tracking pixel before you ever open the message. The “open” is technically real but came from Apple’s servers, not from you. Most ESPs (email service providers) now label these as machine opens and exclude them from engagement scoring.

Will turning off remote images break my emails?

Visually, yes. Functionally, no. The text, links, and structure of every email are untouched. You just see placeholder boxes where the images would be, with a one-click option to load them when you actually want to see them. Most people adjust within a week.

Are there tracking pixels in plain-text emails?

No. Pixels require HTML and remote image loading. A true plain-text email cannot carry one. This is why some privacy-conscious senders deliberately send plain-text only.