OFM Databank
SynthID and AI Watermarks: What Actually Gets You Banned, What Platforms Check, and What Removal Methods Work

AI & Tools

SynthID and AI Watermarks: What Actually Gets You Banned, What Platforms Check, and What Removal Methods Work

Operators are spending real money trying to dodge AI detection — some of it working, most of it guesswork, and a few methods actively making things worse.

Updated Jun 2026 · sourced from 17 YouTube creators and 8 operator groups

Key takeaways

  • Nano Banana Pro embeds a SynthID watermark that survives metadata stripping and screenshots.
  • Instagram reportedly does NOT yet scan for SynthID — TikTok and YouTube sometimes do.
  • OnlyFans bans full AI creators outright; Fanvue explicitly allows them with disclosure.
  • Offline ComfyUI + LoRA generation reportedly passes AI checks; NSFW video still fails even with 96GB VRAM.
  • Operator consensus: 'retaking a photo of the photo' is a real (if crude) SynthID removal method.

An operator drops $1,600 on an unban service. The account is back live inside 24 hours.

Forty-eight hours later, it's gone again — same flag, same detection signal.

The problem wasn't the ban. It was that nobody understood what triggered it.

AI watermarks are the new fingerprint in this space, and most operators are running blind: copying removal tips from group chats, trusting vendors who have skin in the game, and learning the hard way that not all watermarks are equal.

This is what the evidence actually shows.

The Watermark Landscape: What You're Actually Dealing With

There are two fundamentally different types of AI signal baked into your generated images — and they require completely different countermeasures.

Metadata watermarks are EXIF-layer tags: generation timestamps, model identifiers, GPS spoofing artifacts. These are the ones metadata-stripping apps claim to defeat.

Some do.

Perceptual/cryptographic watermarks — of which Google's SynthID is the dominant example — are different. They're embedded into the pixel structure of the image itself, invisible to the eye, and they survive the treatments that kill metadata.

SynthID is specifically the watermark embedded in outputs from Google's Gemini image generation and Imagen models. And here's where it gets messy for OFM operators: Nano Banana Pro runs on Google's infrastructure, which means every image it produces carries SynthID by default.

Multiple operator groups flagged this across early 2026 — one noting explicitly that "metadata apps generate fake iPhone 15 Pro EXIF/GPS to dodge AI detection, but fail on Nano Banana (SynthID watermark)." Another put it bluntly: "Nano Banana embeds SynthID watermark."

Those aren't the same thing as a metadata strip. Not even close.

What Platforms Are Actually Scanning

Here's the most operationally important fact in this article, and it comes with a significant caveat.

Operators in multiple groups, comparing notes from April through June 2026, landed on a rough consensus: Instagram currently does not check for SynthID. One group stated it directly — "SynthID watermark survives screenshots/metadata strips; no normal spoofing removes it, but Instagram doesn't check it yet." Another group in the same period echoed this, describing SynthID removal for Instagram posting as a precautionary step rather than a confirmed necessity.

TikTok and YouTube are a different story. Operator chatter from the same period describes both platforms flagging some AI videos — not all, not consistently, but enough to register.

One group put it this way: "TikTok and YouTube flag some AI videos, not all; Instagram currently doesn't detect SynthID."

This is chatter — anonymous, potentially biased, and definitely not a platform policy document. But the directional signal from multiple distinct groups is consistent enough to be worth acting on.

The vetted evidence adds a harder layer. (Bjorn Olsen, Dec 2025) makes a point that operators consistently underweight: detection isn't binary. Accounts that appear to be evading AI detection may simply be receiving leniency — the platform has flagged them and is watching, not acting.

Platforms use hash fingerprinting and multiple detection layers beyond pixel analysis, and what looks like a clean run may just be a delayed enforcement queue.

OnlyFans itself? The platform doesn't appear to be running SynthID-specific scans.

Its approach is blunter: it bans AI creators categorically. (Markuss Hussle, Aug 2025) confirmed this — AI creators are banned from OnlyFans entirely, forcing operators onto alternatives like Fanvue. Multiple operator groups across at least three distinct chat communities corroborated this through 2026, with one adding the useful operational note that "Fanvue permits AI models and now pushes it as the first signup option." (Oliver Smole, Apr 2026) frames the survival strategy: treat AI accounts as inherently temporary, cap them at 20–30% of total agency revenue, and always have a recovery plan.

Nano Banana Specifically: The Pixel Artifact Problem

Beyond SynthID, operators flagged a separate issue with Nano Banana Pro output — detectable pixel artifacts that aren't the watermark itself but still trigger detection systems.

One group in April 2026 described it plainly: "AI-model accounts getting banned because nano pro leaves detectable pixels in generated images." This is distinct from the SynthID signal — it's a quality artifact in the generation output that AI-detection systems (like Sightengine, which one group confirmed Instagram runs) can fingerprint.

Sightengine detection was flagged as an active problem by at least one operator group from late 2025, with a specific warning: undetectable images are needed or accounts get banned, with one operator reporting losing 10,000-follower Instagram accounts to this.

This matters because it means even if you strip SynthID, the underlying image quality signature may still be readable.

Removal Methods: What Works, What Doesn't, What Remains Contested

The Screenshot / Phone Retake Method

The crudest technique in circulation — and, per operator reports, a genuinely functional one for metadata and potentially for SynthID's perceptual layer.

One operator group summarized the logic: "kill SynthID and retake pictures of the pictures with your phone." The idea is that re-photographing re-encodes the pixel data through a real camera sensor, adding authentic EXIF and disrupting the embedded signal.

Does it actually remove SynthID? The honest answer is: operators report it works, but this hasn't been independently verified, and (Bjorn Olsen, Dec 2025) explicitly warns that appearing to pass detection may mean you're being given leniency, not actually evading it.

Screenshot + Canva Re-export

A variation on the above. One operator group in March 2026 described the workflow: screenshot the generated image, run it through Canva, export.

The logic is similar — re-encoding the image data disrupts watermark integrity.

This is lighter than the phone method and faster at scale, but the same uncertainty applies.

Metadata Stripping Apps and Spoofing

The evidence on these is clear: they solve the wrong problem. One group noted that metadata apps with fake iPhone 15 Pro EXIF/GPS data "fail on Nano Banana (SynthID watermark)."

EXIF spoofing addresses the metadata layer. SynthID lives in the pixels.

These are not the same.

Metadata stripping remains useful for content reposting — platforms that flag duplicate content via hash-matching. It does not address AI origin signals.

Spoofer Bots (Patryk, Oct 2025) and multiple operator groups reference tools like @ofmspooferbot for content spoofing across platforms. The explicit use case is duplicate-detection avoidance — making reused content appear new. This is a different problem than AI-origin detection, and operators conflate the two constantly.

Spoofer bots are not SynthID removal tools. They're duplicate-hash disruption tools.

Useful, but scoped.

Offline Generation: The Nuclear Option

This is where the most credible signal lives, and it comes with the highest barrier to entry.

One operator group in April 2026 flagged a workflow that reportedly passes all current AI checks for images: offline generation using Chroma with LoRA models, run locally. The caveat they included is important: "NSFW video still fails detection even with 96GB VRAM."

The logic is sound. If you're not sending image data through Google's servers, you can't receive a Google watermark.

ComfyUI with locally-trained LoRAs has been recommended by both operators and vetted creators for exactly this reason — (Bjorn Olsen, Dec 2025) describes Nano Banana Pro combined with Gemini as a training-image shortcut, but the actual generation moving to local inference is the ban-avoidance play. (Yalla Papi, Jan 2026) documents the LoRA pipeline — training returns five epoch versions, you review all five, discard artifacts, and publish the best.

It's not plug-and-play, but it's clean output.

The tradeoff: setup complexity is high, SFW quality from local models still trails cloud tools, and video generation doesn't currently pass detection regardless of hardware.

Where Operators Disagree: The Conflicts You Need to Know

Does SynthID actually cause bans on Instagram? The dominant operator view in 2026 is that Instagram doesn't currently scan for it. But a dissenting strand exists: one group attributed a wave of AI account bans specifically to SynthID, framing it as the primary trigger. Both positions came from active operators in the same period. The honest read: nobody outside Instagram's trust and safety team knows for certain, and enforcement can change overnight.

Is Nano Banana Pro safe for OFM posting? One group calls it the gold standard for SFW image quality with no alternative matching it. Another describes AI model accounts getting banned specifically because of Nano Banana pixel artifacts. A third notes operators have moved to Seedream or ComfyUI for NSFW precisely because of this risk. Quality leader and ban risk may both be true simultaneously — the answer depends on what you're posting, where, and how frequently.

Does Fansly allow AI content? One group states that Fansly policy explicitly bans photorealistic AI content. Another describes Fansly as a functioning alternative for AI creators. This may reflect policy versus enforcement, or policy changes over the period these groups were active. Verify directly with Fansly support before building on it — one operator group confirmed Fanvue live support will flag an AI model if it looks too young, resetting earned revenue in the process.

Is the phone-retake method actually removing SynthID? Some operators swear by it. The technical counterargument, backed by (Bjorn Olsen, Dec 2025), is that you may not be removing the watermark — you may be getting leniency. These are not equivalent outcomes, and betting an account on the distinction is a real risk.

The Practical Bottom Line

Here's the honest stack ranked by risk profile:

  • Lowest ban risk for AI images: Local ComfyUI + LoRA inference. No cloud watermark possible. High setup cost. Quality gap for SFW closing, but real.
  • Middle ground: Nano Banana Pro with phone-retake or Canva re-export before posting. Works for Instagram per current operator consensus. Not guaranteed.
  • Highest risk: Raw Nano Banana Pro or Gemini output posted directly to any platform without processing. SynthID intact, pixel artifacts intact, detection risk highest.
  • Platform routing: Pure AI creators belong on Fanvue (with disclosure) or dFans (Patryk, Dec 2025), not OnlyFans. This isn't a detection conversation — it's a terms-of-service conversation. OnlyFans bans full AI creators at the account level, not the image level.

For marketing content specifically — SFW images for Instagram traffic funnels — the detection environment is apparently permissive right now (Patryk, Feb 2026). That changes.

Build workflows that assume enforcement tightens rather than workflows that depend on current leniency.

One number that should anchor your risk tolerance: per operator chatter, roughly 5% of AI TikTok accounts aren't immediately identifiable as low-effort AI content. That's not a passing grade.

That's a very loud signal about how early this technology still is — and how fast platforms are catching up.

Sources

On the record (YouTube creators):

  • Bjorn OlsenHow to Create a High-Converting Fanvue Profile for AI OFM model, Dec 2025. Watch ↗
  • Bjorn OlsenHigh-Quality AI OFM Models Using Gemini 3 + LoRA Training Method, Dec 2025. Watch ↗
  • Oliver SmoleThe Truth About AI Creators in OFM (2026), Apr 2026. Watch ↗
  • PatrykTools I use in my OFM Agency (2025), Oct 2025. Watch ↗
  • PatrykThe Best Platform for AI Creators - dFans, Dec 2025. Watch ↗
  • Markuss HussleAI OnlyFans Management | What No One’s Telling You, Aug 2025. Watch ↗
  • PatrykHow AI can make you $50k/month (OFM), Feb 2026. Watch ↗
  • Yalla PapiHow I Make AI Content From Real Models (LORA TUTORIAL), Jan 2026. Watch ↗

Community intelligence: 139 operator claims aggregated from 8 separate private OFM groups (Dec 2025–Jun 2026), corroboration counted across groups. Group identities are withheld to protect sources; browse the underlying intel in the Community Intel Wiki.