-
Notifications
You must be signed in to change notification settings - Fork 0
Getting Started

Welcome! This guide will walk you through the basics of installing and using Content Inspector Pro.
- Visit the Unreal Engine Marketplace
- Search for Content Inspector Pro
- Click Install to Engine
- Select your Unreal Engine version
- Once installation completes, restart your Unreal Editor
The plugin will automatically appear in your editor after restart.
- Open your Unreal Engine project
- Go to Edit > Plugins
- Search for "Content Inspector Pro"
- Make sure it's enabled (blue checkmark)
- The editor may ask you to restart—click Yes

- In the Content Browser, navigate to any folder (e.g.,
/Content/Assets) - Right-click on the folder
- Select "Scan with Content Inspector Pro"
- Wait for the scan to complete

- Open the Content Inspector Pro panel (Window > Content Inspector Pro)
- Click the folder icon to select a folder to scan
- Choose your target folder (e.g.,
/Content) - Click "Start Scan"

Once a scan completes, you'll see results organized by severity in a table organized into columns:
- Checkbox: selects which asset(s) you want to fix.
- Severity: the issue severity level.
- Rule: the rule that triggered the issue.
- Asset: the affected asset.
- Message: what was detected.
- Fix: how it can be resolved (suggested or automatic fix).
- View: action/button to show the asset in the Content Browser.
Usage notes:
- Hovering any cell shows the full text if it doesn’t fit.
- Double-clicking any row also navigates to the corresponding asset in the Content Browser.

Content Inspector Pro includes 7 built-in rules:
Validates asset naming conventions based on prefix rules. Perfect for enforcing team naming standards.
Example: Detects if a texture is missing a prefix like T_ or TX_
Audits texture compression settings to ensure optimal performance and quality.
Example: Detects incorrect compression formats
Checks if textures exceed your project's maximum size limits.
Example: Flags 4K textures when your limit is 2K
Validates that texture dimensions follow Power of Two (POT) standards.
Example: Detects 1024×512 textures instead of standard 1024×1024
Audits LOD (Level of Detail) setup on static meshes.
Example: Detects meshes missing LODs or with incorrect LOD distances
Detects orphaned or problematic asset redirectors.
Example: Finds broken redirects that can slow down editor performance
Finds empty folders in your project structure.
Example: Detects unused /Content/Temp/Old Assets/ folders
- After running a scan, click "Export Report".
- The report is generated and saved in these formats:
- CSV — Excel-compatible spreadsheet
- JSON — For automated processing
- HTML — Interactive, shareable report
- The save location appears in the text below.

HTML reports are perfect for sharing with your team:
- Open in any web browser
- No special software required
- Professional presentation

- Open Window > Content Inspector Pro
- Click "Settings" or "Configure Rules"
- Toggle rules on/off based on your needs
- Adjust rule parameters as needed
Adjust how severe each issue is categorized:
- Rules can be marked as Info, Warning, or Error
- Customize based on your pipeline needs
- Changes apply immediately to future scans
- 🐛 Report issues on GitHub Issues
- 💬 Ask questions in Discussions
- 🎮 See plugin in action: Video Demo