Brave's desktop browser now removes an identifier beginning with "FBMD" that Meta writes into the metadata of Facebook and Instagram photos. Brave announced the change on November 12, 2026, and PPC Land reported on it on November 14. The direct effect on Meta ad campaigns is likely small, but it fits a broader trend of browsers removing identifiers.
What changed
From version 1.98, Brave on desktop deletes the FBMD value when a user saves a Facebook or Instagram image, and uploads a cleaned copy when a user uploads one. The original file on the user's disk is not modified. Android and iOS support is planned but has no date.
The value sits in the IPTC Special Instructions field of the image. The International Press Telecommunications Council documented it back in 2019 and found it survived a re-upload by a second user. Brave's GitHub issue on the topic was opened in July 2019 and closed in October 2026.
What Meta uses it for
Nobody outside Meta knows for sure. Meta has not documented the identifier publicly, and Brave itself says it is possible Meta does not use it for tracking. Brave's explanation on LinkedIn was blunt: "Meta hasn't said what the identifier is for" (Brave).
Brave's reasoning is that the ID could make it easier to link the same photo across different accounts. That is the same class of signal behind identity resolution, which underpins cross-platform targeting and measurement.
Impact on advertisers
PPC Land describes the direct campaign effect as hard to measure and probably small. The change does not touch the Meta Pixel, the Conversions API or any ad product.
The bigger point is direction of travel. Browsers keep removing identifiers, and Meta keeps moving measurement toward signals it controls, such as its on-device conversion measurement setting that was scheduled to switch on by default on November 12 for datasets already sending events. Measurement built on your own first-party data holds up best as these changes pile up.
What it means for you
- No action is needed in Ads Manager for this change
- Do not rely on browser-side signals alone; keep the Conversions API sending server events
- Check that your Event Match Quality is healthy going into Black Friday
- Expect more browsers to strip undocumented identifiers over time
