Reduce a supported SVG conservatively
SVG Optimizer creates a conservatively serialized copy of supported local SVG artwork and compares its rendered pixels with the admitted source. It is useful when you want to keep a vector document while reducing avoidable representation overhead. It is not a design simplifier, a universal sanitizer or permission to strip every piece of descriptive information from an unfamiliar file.
Choose a file or paste SVG source, then read the inspection. The application accepts a restricted static subset. It does not insert arbitrary uploaded markup into the live page. A source that a full browser or illustration package can display may contain features outside this workflow and be refused before optimization.
Safe mode preserves meaningful structures
The current conservative mode preserves comments, metadata, identifiers, viewBox, title and description elements, ARIA information, paths and references. These can matter for accessibility, attribution or document structure even when they do not change the visible picture. Optimization here does not mean deleting everything that appears unnecessary in a thumbnail.
An identifier may be referenced by a local gradient, clipping path or another allowed construct. Removing or renaming it carelessly can change the rendering or break a document used elsewhere. The tool's restrained approach is intended to reduce accidental semantic damage rather than maximize a percentage at any cost.
For a hand-authored icon, the savings may be modest. For another admitted document, serialization may remove avoidable textual overhead. Read the actual measured bytes. A smaller number is not a stronger result if the document's meaning or visible appearance has been changed, and the tool should not invent savings where none were obtained.
Active content remains outside the policy
Scripts, event attributes, foreignObject, animations, filters and external or data references are refused by the shared SVG platform. Imported or escaped CSS and unsupported namespaces are also outside the accepted scope, as are document type declarations and entities. This is a constrained local workflow, not a complete implementation of the SVG specification.
Do not interpret an accepted output as a certificate for unrestricted embedding into every security context. The source has been admitted under this tool's rules and rendered in an image context. A larger application can have additional requirements about accessibility, licensing, semantics and where its resources are allowed to load.
If a source is rejected, use a compatible editor to produce a self-contained supported document where appropriate. Do not simply remove the extension or copy the same markup into another live page to bypass the refusal. A familiar logo or simple-looking thumbnail does not describe every feature present in the underlying XML.
Rendered comparison is deliberately scoped
The optimizer performs an independent rendered-pixel comparison between the admitted source and candidate output. That is a useful check for visual regressions at the selected verification dimensions. It is not proof that every possible viewport, font environment or downstream SVG interpreter will behave identically.
Choose verification dimensions that are relevant to the intended use. The width and height controls here support bounded rendering checks; they are not a promise that optimization changes the artwork's intrinsic design to that size. A dimensionless source still needs a deliberate rasterization size for comparison.
Inspect the result visually as well as reading the check. Small text, fine lines, clipping and transparent intersections deserve attention. A pixel comparison can only evaluate the representation actually rendered. External facts such as whether a title is accurate or whether a logo is licensed remain outside its scope.
Keep vector and raster goals separate
If the recipient needs PNG, use SVG to PNG. It converts supported artwork into a chosen raster grid and no longer supplies editable paths. This optimizer instead aims to retain a supported SVG document, with its vector structure and preserved descriptive elements.
Editor offers a different, narrower editable vector-import subset. A successful optimized rendering does not mean that every allowed SVG construct can be edited there as independent shapes. When editability is the goal, assess the actual Editor import rather than using a successful rendering check as a substitute.
For web use, also consider the surrounding page. An SVG can be small while the site loads unnecessary scripts or oversized photographs. Optimization of one file is not an overall performance certificate or a guarantee of improved search position. Keep the file's purpose and the page's behavior as separate decisions.
Metadata preservation is intentional
This safe mode does not promise to remove private descriptive fields. Comments and metadata can contain names, editing notes or credits that you should review before public distribution. Preserving them protects legitimate information but also means that optimization is not the metadata-cleaning workflow for arbitrary SVG documents.
Visible names and marks also remain part of the artwork. A vector document can disclose information through both its rendered image and its text source. Review both when privacy matters, and retain attribution or licensing information that you are required to keep. The application does not decide those obligations for you.
Complete the job with a saved-file check
Configured admission is 2 MiB of SVG source, 10,000 nodes and depth 64. Rendering verification remains bounded by the shared pixel and edge limits and available browser resources. Compact XML can still describe substantial work, so these limits should not be bypassed because a file looks visually simple.
Read the output and verification status, then download the optimized SVG or use the copy-source action when that is the intended handoff. Open the actual saved file in the receiving application and inspect the important features. A download request is not proof of completion. Keep the original until you have confirmed that the conservative result meets both its visible purpose and any structural requirements beyond this tool's comparison.