

<strong>Svigent SVG Engine Settings Screen:</strong> Intuitive configuration with live security status badge and 1-click selector copy helper.
Svigent SVG Engine adds secure SVG support to WordPress. Upload SVG and SVGZ files to the Media Library, and every file is sanitized before it is saved. Then turn any SVG image into inline SVG so you can recolor and animate it with CSS.
WordPress blocks SVG uploads by default because an SVG file is XML and can hide JavaScript, which leads to Cross-Site Scripting (XSS) and XML External Entity (XXE) attacks. Svigent SVG Engine removes those risks on upload, so you can use sharp, lightweight vector logos, icons, and illustrations without opening a security hole.
enshrined/svg-sanitize library. Scripts, event handlers, remote references, and dangerous XML entities are stripped before the file reaches your server. Sanitization is always on.style-svg to an image and the plugin swaps the <img> for real <svg> markup, so fill: currentColor, hover effects, and CSS animations just work.viewBox, width, and height on upload so SVG images keep the right aspect ratio in Gutenberg, page builders, and themes.srcset for SVG files to save disk space.Svigent SVG Engine uses the same style-svg class that many SVG plugins use for inline SVG, so existing images keep working. Deactivate your old SVG plugin, activate Svigent SVG Engine, and enable Frontend Inline Rendering in Settings Svigent SVG Engine.
Svigent SVG Engine does not track users, collect data, or connect to any external service.
svg_flow_allowed_tags and svg_flow_allowed_attributes: adjust the tags and attributes kept during sanitization.svg_flow_user_can_upload: decide who can upload SVG files.svg_flow_inline_allowed_urls: allow the inliner to load SVGs from a CDN.svg_flow_max_inflated_size: change the maximum decompressed size for SVGZ uploads.svgflow:inlined: a JavaScript event fired on each SVG after it is inlined.