Native SVG support was originally on the Documoto roadmap but was later bumped off, and I’d like to advocate for bringing this feature back. Our company relies heavily on SVG-based technical illustrations, especially for exploded diagrams, and the current workflow creates several limitations.
Right now, when we upload an SVG to Documoto, the system rasterizes it into a static image. This removes many of the advantages that make SVG the preferred format for technical content:
•No true scalability — images become blurry when users zoom in
•Loss of clarity for detailed assemblies and small parts
•Larger file sizes compared to vectors
•Inconsistent quality across different screen resolutions
Exploded diagrams benefit significantly from vector rendering, since users frequently zoom in to identify small fasteners, hidden components, or narrow callouts. Rasterization directly impacts accuracy and usability.
•Native SVG rendering would provide:
•Perfect clarity at any zoom level
•Better user experience for parts identification
•Better performance due to smaller file sizes
•Preservation of authoring quality (no more raster conversion)
•Alignment with modern documentation and publishing standards
Given that this was previously planned, our company would like to express strong interest in having native SVG support reinstated on the development roadmap. This enhancement would significantly improve the quality and usability of our parts pages and support more precise, scalable technical content moving forward.
Looking forward to hearing whether this can be reconsidered for future development.