Photoshop’s Remove Tool allows you to bypass cloud moderation blocks entirely by executing machine learning tasks locally on your device’s GPU, NPU, or CPU. Unlike Generative Fill, which sends active canvas pixels to external Adobe servers for processing, the Remove Tool can run purely on local hardware when configured correctly. This makes it the primary solution for retouching skin folds, archival damage, historical assets, and high-contrast silhouettes that consistently fail cloud content safety policies.
Fast Fix
Select the Remove Tool (J) from the toolbar, uncheck Use Generative AI (or select Never / When Needed in the tool options bar), set your brush size, and paint directly over the unwanted element. The tool replaces the object using local machine learning without sending pixels to Adobe servers or triggering safety filters.
Cloud Generative Fill vs. Local Remove Tool
Understanding the technical divide between Adobe’s cloud AI and local processing engines prevents hours of wasted troubleshooting.
| Feature | Cloud Generative Fill | Local Remove Tool |
|---|---|---|
| Processing Location | Adobe Cloud Servers | Local Device (GPU / NPU / RAM) |
| Moderation Engine | Active (Strict Cloud NSFW & IP Filter) | None (Executes directly on canvas) |
| Internet Requirement | Constant high-speed connection | Works completely offline |
| Generative Credits | Consumes monthly allocation | Consumes zero credits |
| Prompt Input | Text or blank contextual synthesis | Brush input only (object replacement/fill) |
| Primary Use Case | Complex element creation / canvas expansion | Blemish, object, and artifact removal |
For a complete technical analysis of these two distinct environments, review The Difference Between “Cloud Safety” and “Local Safety”.
Configuring the Remove Tool to Run Completely Locally
Recent Photoshop updates allow the Remove Tool to toggle between local models and Firefly-powered cloud processing. To bypass content blocks, you must ensure the tool does not ping the cloud.
Photoshop Options Bar (Remove Tool Active)
┌────────────────────────────────────────────────────────────────────────┐
│ Size: [ 45 ] | Mode: [ In-Device Only ▼ ] | [X] Sample All Layers │
└────────────────────────────────────────────────────────────────────────┘
- Select the Remove Tool from the nested healing tools palette (J).
- Look at the Options Bar across the top of your workspace.
- Locate the Processing Mode or Use Generative AI dropdown.
- Change the setting from Generative AI (Cloud) or Auto to In-Device Only (or uncheck the cloud toggle depending on your Photoshop version).
- Ensure Sample All Layers is checked so you can work non-destructively on an empty layer.
If the Remove Tool UI is unresponsive or greyed out after adjusting these settings, consult Why “Remove Background” UI Buttons are Unresponsive to verify panel and layer state integrity.
Step-by-Step: Retouching Blocked Content Non-Destructively
Follow this sequence to clear blemishes, clothing wrinkles, or sensitive background elements that previously caused a “Content Violation”:
1. Setup Your Non-Destructive Workspace
Never paint directly onto the locked Background layer. Working on a separate layer lets you erase and blend your results without degrading original assets.
- Open your document.
- Click the New Layer icon at the bottom of the Layers Panel (Ctrl+Shift+N on Windows, Cmd+Shift+N on macOS).
- Name this layer
Retouch_Local. - With the Remove Tool active, verify that Sample All Layers is enabled in the Options Bar.
2. Stroke Application and Overlap
The local machine learning model requires surrounding boundary pixels to infer depth and texture.
INCORRECT CORRECT
(Paint inside edges only) (Overlap edges by 5-10px)
+-------------+ +-------------+
| /////// | | /////////// |
| ///////// | |/////////////|
| /////// | | /////////// |
+-------------+ +-------------+
Results in blurring Clean texture synthesis
- Adjust your brush size using the bracket keys (
[and]). Set the brush slightly larger than the artifact or shadow crease you want to remove. - Paint over the target element. Make sure your stroke extends roughly 5 to 10 pixels beyond the edge of the object into the clean background.
- If Remove after each stroke is enabled in the options bar, release your mouse button to execute the replacement immediately.
- If it is unchecked, paint all desired regions and click the blue Commit (Checkmark) button in the contextual task bar.
3. Handling Complex Lighting and Skin Folds
When Generative Fill blocks an edit on a skin contour or deep shadow fold, attempting to paint over the entire fold at once with the Remove Tool can occasionally cause smudging.
- Zoom in to at least 100% (Ctrl++ / Cmd++).
- Work in short dabs rather than continuous dragging strokes.
- Remove individual shadow nodes first, working from the outside edges inward toward the center.
- If a seam remains visible, select the Healing Brush Tool or Clone Stamp Tool set to Current & Below with 30% flow to soften the transition.
Hardware Optimization: When Local Processing Lags
Because the Remove Tool calculates object replacement on your local system, processing speed is determined entirely by your workstation’s hardware.
Workstation Hardware Allocation for Local AI
│
├── High-End System (NVIDIA RTX / Apple Silicon M-Series)
│ └── Processing takes 1–3 seconds per stroke.
│
└── Low-Spec System (Integrated GPU / Low RAM)
└── System hangs, fans spin up, strokes take 15+ seconds.
If your local processing hangs or stutters:
- Verify GPU Acceleration: Go to Edit > Preferences > Performance (Windows) or Photoshop > Settings > Performance (macOS). Ensure Use Graphics Processor is checked.
- Allocate Adequate System RAM: In the same Performance menu, verify that Photoshop is allocated at least 70% of available system memory.
- Switch Engines if System Crashes: If your local machine lacks sufficient VRAM and crashes during processing, see How to Switch Between “Cloud” and “Local” AI Engines to calibrate hardware allocation or optimize processing switches.
What to Do if You Get Locked Out of AI Features
If you switch back to Generative Fill later and discover that the entire interface is frozen or flagging harmless prompts, your session may be stuck in a cached moderation loop.
- Do not continue submitting alternative prompts; clear your session buffer.
- Review Fixing the “Violation” Loop: When Every Prompt is Blocked to break the caching deadlock, reset the Photoshop OOBE interface, and safely re-establish cloud server communication.