Safe SVG

Quick take

A sensible default for WordPress sites that genuinely need SVG uploads. It solves the core security concern rather than treating SVG as just another image MIME type.

Best fit: Site owners and development teams that need SVG uploads but want sanitization to be the default rather than simply enabling the SVG MIME type. I would choose a different option for sites that do not need SVG files at all or workflows that require preserving every unsupported or remote SVG reference exactly as supplied.

SVG files are flexible and sharp at any size, but they can contain scripts, remote references, and XML constructs that should not be trusted blindly. Safe SVG addresses the security problem instead of only changing WordPress upload permissions.

How it works

Safe SVG enables SVG uploads while sanitizing the files before use. It also provides SVG previews in the Media Library, optional SVGO optimization, and newer inline SVG block capabilities.

Uploaded SVG files are passed through sanitization before they are accepted into the Media Library. The plugin can also preview SVGs in WordPress and offers optional optimization and inline rendering tools for supported workflows.

Features that matter

• Sanitized SVG uploads: Allows SVG uploads while cleaning potentially unsafe markup before storage.
• Media Library SVG previews: Shows SVG assets clearly inside the WordPress Media Library.
• Optional SVGO optimization: Can reduce unnecessary SVG markup when optional optimization is enabled.
• Inline SVG block support: Provides a block workflow for rendering SVG markup inline when needed.
• Upload-time security filtering: Runs sanitization during the upload process instead of relying on manual cleanup.
• Controls for remote SVG references: Adds controls for handling external references inside SVG files.

Sanitization is the main reason to use it

The important distinction is that Safe SVG does not merely permit SVG uploads. It sanitizes the markup before use, which addresses the main security concern with allowing arbitrary SVG files in the media library.

Where the trade-offs show up

Sites that do not need SVG files at all or workflows that require preserving every unsupported or remote SVG reference exactly as supplied should compare alternatives carefully. Sanitization can remove unsupported or unsafe markup. Some advanced SVGs need testing after upload. Not needed if the site can avoid SVG uploads entirely.

Practical considerations

The safest SVG workflow still starts with trusted source files. Sanitization reduces risk, but administrators should also control who can upload media and review unusual SVGs before publishing them. If a design only needs a small number of static icons, using pre-reviewed assets can keep the workflow simpler than opening SVG uploads broadly.

Pricing

Safe SVG is free on WordPress.org.

Who should consider it

Site owners and development teams that need SVG uploads but want sanitization to be the default rather than simply enabling the SVG MIME type.

What to compare before choosing

SVG Support is the closest comparison and adds a more explicit advanced mode for inline styling and animation. Safe SVG is the cleaner choice when sanitization and secure upload behavior are the main priorities.

PluginSuggest verdict

A sensible default for WordPress sites that genuinely need SVG uploads. It solves the core security concern rather than treating SVG as just another image MIME type.

Safe SVG FAQs