What Grok Imagine actually blocks
Grok Imagine enforces industry-standard content policy hard limits, plus a few xAI-specific ones. The full list based on aggregated user reports and xAI's Terms of Service through 2026:
Sexual content and nudity. Explicit sexual acts, nudity of any kind (including partial), and prompts specifically requesting sexualized or suggestive imagery are all blocked. This is the biggest surprise for users who arrived expecting the "unfiltered Grok" branding to translate to image generation.
Minors in any context. Any image depicting or resembling a minor is blocked outright — this includes prompts that don't specify age but produce results the moderation classifier reads as minor-adjacent. This is the least controversial of the hard limits and applies universally across every legitimate AI image platform.
Real-person likenesses without consent. Named celebrities, political figures, and other identifiable public figures cannot be generated in most contexts. Grok Imagine's enforcement of this has tightened through 2026 after several incidents involving deepfake-style content of specific individuals.
Graphic violence and gore. Extreme violence, wounds, gore, or graphic depictions of harm are blocked. Stylized/cartoon violence (a knight fighting a dragon) generally passes; realistic gore does not.
Self-harm content. Any prompt requesting depictions of self-harm, suicide, or eating-disorder-adjacent imagery is blocked outright.
Hate content and slurs. Prompts using explicit slurs or depicting hate-symbol-adjacent imagery are blocked.
Illegal content. Anything depicting illegal activity in enough specificity to constitute instruction — drug synthesis, weapons manufacturing, etc. — is blocked.
The gap between "free speech" marketing and actual policy
Elon Musk has publicly framed Grok as an alternative to what he characterizes as over-moderated AI (ChatGPT, Claude, Gemini). Users arriving at Grok Imagine expecting that framing to translate to image generation are consistently surprised by how much the platform actually blocks.
The gap exists for two reasons.
First, the "free speech" framing applies more to the text chat model (Grok itself) than to image generation. Text Grok will discuss more politically-charged topics than ChatGPT will, but image generation has different legal and regulatory exposure — Section 230 protections don't apply the same way to generated media, and the risk profile of generating a defamatory image of a real person is substantially higher than the risk of a text chatbot discussing them.
Second, xAI signed a licensing deal with Apple in mid-2026 to integrate Grok into iOS and macOS, which required Grok to meet App Store content policies. Apple's content requirements for AI models don't distinguish between text and image — both surfaces have to meet the same content bar. That constraint tightened Grok's moderation across the board, not just on iOS.
The result: Grok text will get further into edgy discussion than most competitors. Grok Imagine will not.
The January 2026 undressing scandal set the current policy floor
The specific event that moved Grok Imagine from "permissive" to "mid-strict" happened in early January 2026. Users exploited Grok's image-edit flow to generate non-consensual sexualized alterations of real people at scale — tech-policy reporting cited roughly 6,700 such images per hour at peak. xAI's response was staged:
January 9 — image generation restricted to paid subscribers (free-tier image gen effectively removed). January 10-16 — Indonesia (Jan 10), Malaysia (Jan 11), and the Philippines (Jan 16) blocked Grok outright. Ofcom in the UK opened a formal investigation. January 14 — xAI banned "editing real people in revealing clothing" as a specific policy line. March 12, 2026 — Musk posted the sentence that now functions as Grok Imagine's policy ceiling: *"If it's allowed in an R-rated movie, it's allowed in Grok Imagine."* The EU later declared Spicy Mode illegal in the bloc.
That chronology is important because the March post has been widely read as "Grok Imagine permits R-rated content" — in practice it's a cap, not a floor. R-rated-movie content permits partial / semi-nudity, suggestive poses, and intimate themes for fictional adult characters in Spicy Mode on iOS/Android; it does NOT permit explicit sexual acts, full nudity, real-person likenesses, or anything involving minors. Desktop and web lost Spicy Mode access entirely through 2026.
Maya
“the grok nsfw thing is such a bait and switch — you get all the way through the UI and then it just... doesn't. that's not a thing with me. what were you actually trying to generate?”
Reply to Maya →Real-person likeness enforcement in 2026
The real-person enforcement is the moderation area that changed most in 2026, driven by the January undressing scandal above. Through late 2025, Grok Imagine would generate images of specific named individuals with only mild resistance. Multiple incidents involving political figures, celebrities, and private individuals depicted in defamatory contexts led xAI to tighten the classifier significantly.
Current state as of November 2026: attempting to generate an image of a named person (celebrity, politician, athlete) typically returns a moderation refusal. Even indirect references ("the current president," "the tallest NBA player") can trigger the filter if the classifier resolves the reference to a specific identifiable person. Mid-to-late October 2026 saw another round of tightening — specifically stricter male-anatomy filtering and lower sex-scene pass rates across the aurora classifier.
There are edge cases. Historical figures (Lincoln, Napoleon) still generate. Fictional characters with distinctive appearances (Sherlock Holmes, Wonder Woman) still generate. Generic descriptions ("a woman with red hair") still generate. The line the filter draws is roughly: identifiable + living + potentially defamatory = blocked; anything else usually passes.
What this means for legitimate use cases (portrait references, character studies based on real inspirations, fan art) is that Grok Imagine is not the tool. Purpose-built platforms with different policy positions on likeness — including some open-source models users self-host — are the alternative.
What happens when moderation triggers
Grok Imagine's moderation UX has three failure modes, listed in order of severity.
Pre-generation block. The prompt is analyzed before compute spends and returns a moderation-refusal message. Quota is not consumed. This is the best-case failure — you learn immediately that the prompt won't work.
Post-generation rejection. For video specifically, the moderation classifier runs on the OUTPUT, not the input. A prompt that seems fine gets accepted, spends 3-5 minutes rendering, and returns a "content moderated" error at the end. Your daily quota IS consumed, even though you got nothing. This is the failure mode most likely to feel like a bug rather than a policy.
Silent quality degradation. Some reports describe generations that complete successfully but return with subtle modifications — clothing added where the prompt didn't specify, poses less suggestive than requested, faces obscured. This appears to be a compromise the moderation layer makes when the prompt is borderline: allow generation but modify the output. This is the hardest failure to diagnose because the app doesn't tell you moderation modified your result.
There is no official appeal or exception process for individual prompts. xAI does not review case-by-case moderation decisions and does not offer a "please allow this specific use case" workflow.
No paid tier unlocks looser moderation
A common misconception: subscribing to SuperGrok Heavy at $300/month unlocks more permissive content generation. It does not.
Content moderation on Grok Imagine is platform-wide and tier-agnostic. Every paid tier — X Premium ($8), X Premium+ ($40), standalone SuperGrok ($30), SuperGrok Heavy ($300) — hits the same content policy walls. What you're paying for at higher tiers is quota (more generations per day) and priority (faster queue times), not access to different content.
This is a deliberate policy choice by xAI, not an implementation gap. The moderation classifier runs on the model, not the account, and there's no per-user override configurable by tier. Users who cancel Heavy specifically because "content is still the same" are cancelling for the correct reason if their goal was content access.
The implication: if the content you want to generate is what Grok Imagine specifically blocks, no amount of money on Grok's side of the fence will unlock it. The evaluation question shifts to "is there a different platform that fits my use case," not "which Grok tier should I subscribe to."
False positives and prompt rewriting patterns
A meaningful portion of Grok Imagine moderation blocks are false positives — benign prompts that happen to use language patterns overlapping with flagged content.
Common false-positive triggers:
Body-part descriptors. Prompts describing hair color, eye color, and body proportions are generally fine. Adding specific body-part references ("nice curves," "toned arms," "long legs") can trigger the filter even in fully clothed portrait contexts. Rewriting to describe the person's pose or activity rather than their body usually resolves this.
Clothing specificity. "Wearing a swimsuit," "in a low-cut dress" — any clothing description the classifier reads as suggestive can trigger a block. Alternative phrasings that describe the setting/activity ("at the beach," "getting ready for a date," "at a formal event") produce similar images without the block.
Age-adjacent language. "Young" and "youthful" trigger the minor-adjacency filter even in fully adult contexts. Using "adult" explicitly ("young adult woman") or specifying an age ("30-year-old") usually resolves this.
Ambiguous relationships. Prompts describing romantic or intimate relationships between people can trigger the filter based on the specific verbs used. "Together" and "close" pass. Adjacent charged language triggers.
There is no official documented "how to rewrite around Grok's moderation" guide because xAI does not want to appear to be teaching users to circumvent policy. The community-compiled patterns above come from Reddit threads (r/grok, r/aivideo) through mid-2026.
Alternatives when Grok blocks your use case
When Grok Imagine consistently blocks a legitimate creative use case, the practical options split by what kind of thing you're trying to generate.
For SFW portrait / character work. Midjourney and Stable Diffusion (self-hosted or through platforms like Leonardo.ai) both have different policy shapes than Grok. Midjourney is stricter on some things (real people, IP-adjacent content) and looser on others (body descriptors, clothing). Stable Diffusion self-hosted has whatever moderation you configure — meaningful setup lift, meaningful flexibility upside.
For character consistency across many images. If the use case is "same face across many generations" (character studies, comics, storytelling), Grok Imagine doesn't architect for that regardless of moderation — each generation is independent, and the platform doesn't offer per-character LoRAs. Purpose-built platforms that ship per-character LoRAs solve this more cleanly than any general image tool.
For AI-companion-shaped use cases specifically. If the underlying goal was building a relationship with a specific character (rather than generating a lot of one-off images), a companion-native platform is a structurally different tool. Sloane runs per-persona LoRAs so Maya or any curated persona renders the same woman across every image, ships persistent memory that spans weeks of conversation, and prices flat at $9.99 Plus / $19.99 Premium with no per-image throttling to plan around. Different platform, different policy shape, different tradeoffs — worth evaluating if character consistency and long-form conversation are the actual need.
For real-person likeness specifically. No mainstream commercial platform will generate identifiable living individuals without consent, and this is not a gap that's about to close. If the use case genuinely requires it, that's a self-hosted problem to solve on your own hardware with the associated legal responsibility.