Developer Features
Axialis IconVectors was built with developers in mind. Beyond standard vector editing tools, it includes features that streamline integration into modern development environments — from web apps to native applications.
Visual Studio Code companion
Use SVG Editor — Axialis IconVectors to open local SVG assets, static references, inline SVG blocks and icon folders in the desktop editor. Install its bundled Visual Studio Code extension from . File editing uses normal saves. For inline SVG, native saves update the tracked VS Code block automatically by default, with optional review and one Undo step per accepted update. Source conflicts pause the session rather than overwrite newer code. Several inline windows work independently; a confirmed native close ends its binding while unaccepted or unsaved-host artwork remains available for recovery. This does not require AI, MCP or replacing your standard source editor.
Standalone command-line workflows
The Command-Line Interface is a separate
IconVectorsCli.exe (iconvectors-cli on macOS/Linux) for file-based SVG
inspection, syntax checking, PNG/ICO generation, Styles, geometry/color/stroke
changes, stroke outlining and conservative optimization to copies. It does not
open an Editor window or require the MCP bridge.
Versioned command schemas, JSON results, explicit destinations, dry runs and
stable exit codes support IDE tasks, build scripts and local agents. Asset
generation uses the current user’s existing product rights; the CLI does not
activate a license or start a trial.
Live Code Viewer
IconVectors includes a real-time Source Code Viewer that shows the underlying code of your icon as you draw and edit. You can open it from the menu:
- F3
The viewer is read-only, including the SVG tab. Edit the icon on the canvas to update its generated code. To correct a file that fails to open, use the separate SVG source repair dialog (2.20+).
Closing the icon clears the text in every Source Code tab. The viewer can stay open; loading another icon fills the tabs with that icon’s generated code.
Features include:
Live updates as you edit the icon
Tabbed formats: - SVG - Minified SVG - SVG Symbol - XAML (Microsoft format) - WPF Geometry - VectorDrawable - SwiftUI - VueTS - ReactTS - C++
Syntax highlighting for easy readability
Indent Code option to toggle between readable and compact view
Copy button to quickly place the code on your clipboard
In embedded-style mode, normal artwork edits update the stylesheet and class assignments together, including changes made with palettes, library presets and stroke controls. Matching elements can share a definition; changing one can split it from the others. The SVG view shows these automatically maintained styles without local appearance overrides, and Undo restores the artwork and styles together.
Repairing SVG source after an open error
If an SVG cannot be opened, IconVectors reports the reason and offers Edit SVG Source… when the original file can be read as text. Choose it to open Repair SVG Source and correct the source without leaving IconVectors. The message includes a short explanation, the technical error, its location when known, the filename and guidance for inspecting the source. This workflow is available when opening a document, including from File/Open, Recent Files and the built-in Explorer. MCP open requests remain nonmodal: they return an error to the client instead of opening this dialog.
The default-on strict SVG checking option can also find issues before a file would otherwise open. For warnings alone, SVG Source Warnings offers Edit SVG Source… to review them, Open Icon As Is to continue despite them, or Cancel. Open Icon As Is is initially focused and is the default action: pressing Enter opens the icon as-is. An error requires correction before opening with strict checking enabled. Continuing past warnings still uses the normal importer and its mandatory safety checks.
The warning message also offers Don’t show SVG warnings again (disable strict checking), initially unchecked. If you check it and accept Open Icon As Is or Edit SVG Source…, IconVectors immediately saves the strict-checking preference as off. Future Editor opens, including MCP opens and whole-document SVG replacement, then skip these additional errors and warnings. This is not just a popup-suppression setting: basic XML/import safety and all existing batch validation remain in force.
Leaving the checkbox unchecked does not change the preference. In this warning message, Cancel, Escape and the close button do not accept a checked draft. If you opt out and choose Edit SVG Source…, that repair session still uses the strict settings captured for the current open; the saved change applies to future loads. Restore the checks at any time in by enabling Strict SVG syntax checking when opening icons.
The opt-out starts unchecked. Open Icon As Is is the initial Enter-default choice; accepting an open or source-review action applies a checked opt-out.
While you are repairing source or answering an open/save/conflict dialog,
MCP cannot edit the document or run other ordinary tools. Health calls remain
available; finish or cancel the dialog, then let the client inspect the current
state before retrying. A lifecycle_guard response means IconVectors is
waiting for that choice, not that the bridge connection has failed.
The dialog shows the original text with XML syntax colors and line numbers. Its diagnostic list distinguishes errors in red from warnings in amber, with counts and a bounded number of findings. Select a diagnostic to navigate to its source location. The selected issue uses a tinted line background and a margin marker where its location is known, with an explanation and any reliable spelling suggestion. Standard text editing, Cut/Copy/Paste, Find and Undo/Redo apply to the repair buffer; they do not change the current Editor document.
The selected warning enables Apply Suggestion for its misspelled name. Two other invalid attribute values still block Load Icon and need correction.
Use Ctrl+F (Command+F on macOS) to open the inline Find bar. Previous and Next move between matches; F3 and Shift+F3 find the next or previous match while this dialog is active.
Read the diagnostic and correct the affected text, or use Apply Suggestion for a warning with a safe suggested name.
Wait for the automatic check, or choose Check Now.
When no blocking error remains, choose Load Icon.
Review the imported artwork in the Editor, then use Save or Save As to write the repaired version.
Load Icon runs the actual import, including the normal canvas-size rules. If another import problem is found, or you cancel a size conversion or document replacement, the repair dialog retains your text so you can continue. If the current Editor document has unsaved changes, its normal save decision still applies before replacement.
Cancel, Escape and the dialog’s close button leave the original file and current Editor intact. If you have edited the repair text, IconVectors asks whether to Discard Changes or Keep Editing. Escape closes an open Find bar first. Enter inserts a newline in the source editor; it does not load the icon.
Understanding the checks and error locations
Automatic checks run after a short pause in typing, approximately 400 ms. Changing the text immediately disables Load Icon until the current text has been checked. Checks cover XML well-formedness, the SVG root and supported numeric/path syntax. With strict checking enabled, they also check known SVG names and common attribute/inline-style value grammar, including paints, stroke settings, lengths, transforms and gradients. The repair session keeps the setting captured when it was opened.
Definite malformed values of known attributes are errors. Unknown names and possible name typos are warnings, with suggestions where reliable. Valid modern expressions or unsupported features that the bounded checker cannot fully assess are warnings, not proof that the SVG is invalid. Review these findings against the intended artwork; no automatic source correction is applied. Errors disable Load Icon; warnings alone permit it.
With warnings alone, Load Icon remains available. Use Apply Suggestion to correct this selected name, or choose to continue loading after review.
Checks have resource limits so complex input cannot start an unlimited validation job; a skipped or incomplete check is not a success. Use Check Now when the dialog requests a manual check.
An XML error’s line and column identify where the parser detected the problem. The cause can be earlier, such as an unclosed tag. Only the first XML error is reported at a time; correcting it can reveal another. For SVG path or attribute errors, the highlighted line can identify the containing element rather than the exact bad character. Some compatibility errors have no reliable source location, so they appear as messages without a misleading highlight.
A ready state means there are no blocking errors in the implemented checks; warnings may still need review. This is not a complete SVG/CSS standards check or a promise that every browser feature is editable in IconVectors. Final import can still reject unsupported code. These checks run locally and do not fetch external DTDs or other remote resources. They do not change the existing validation used by batch processing.
When the current check reports no errors and no warnings, a green circle with a white check appears at the top beside the bold message The SVG code is clean and ready to open. You can now choose Load Icon; the notice itself does not load or save anything. Warnings alone still allow loading, but keep their warning notice instead of this clean confirmation.
A completed check with no errors or warnings shows the green clean-ready notice. Load Icon still performs the final import.
Unreadable or corrupt/binary content must have its file-access or encoding problem resolved before source editing can be offered. If an encoding is supported by the normal importer but not by this checker, IconVectors reports that checking limitation and can use the normal import path; it does not invent a decoded repair buffer or label a readable encoding as corrupt.
Applying a suggested correction
Select a warning with a concrete spelling correction in the diagnostic list, then click Apply Suggestion. Its tooltip describes the proposed change. The button changes only that selected attribute, element or inline CSS property name, preserving values, quotes and unrelated formatting. For a paired element tag, its opening and closing names are corrected together.
The correction is one text Undo/Redo action, even when it updates both tags. Checking restarts immediately after applying it. Other errors or warnings can remain, so review the refreshed list before choosing Load Icon. Applying a suggestion edits only the repair buffer; it neither saves the original file nor loads the icon automatically.
Apply Suggestion is disabled while checking or loading, for errors, and for advisory or unsupported-feature warnings without an exact safe correction. If a suggestion cannot be mapped reliably to the current source, edit the text manually. IconVectors does not replace every matching name across the file.
Saving a repaired icon
After Load Icon succeeds, the icon is marked modified. The original path remains its normal Save destination, but no source file has yet been written. Use Save As if you want to keep the original separately. Normal SVG import and saving can normalize formatting and structure; source repair does not promise byte-for-byte preservation after saving.
The first save must be explicit even if Explorer > Auto Save Icons is on. Opening another Explorer icon instead follows the normal unsaved-change decision until you save the repaired document. After that first successful save, the ordinary Auto Save behavior applies again. If another application changes the original file before your first save, resolve the reported conflict or use Save As rather than overwriting it unknowingly.
Undo/Redo in the loaded Editor applies to subsequent artwork edits. Undoing those edits does not turn an unsaved repair into a saved document. Automatic recovery copies are separate from saving the original; a recovered repair still requires an explicit save.
Developer Code Targets
The following code targets are available directly from the Source Code tabs and are intended for framework-specific integration:
SVG This is the canonical editable output and matches the internal document model. Use it when you need full fidelity, clean interoperability with design tools, and long-term maintainability. It is also the best baseline for versioning and review in source control.
SVG Minified This output removes extra whitespace and reduces numeric precision to reduce payload size. It is ideal for production web delivery where transfer size and parse time matter. Keep the regular SVG as your source and generate minified output for deployment artifacts.
XAML This target converts vector data to Microsoft XAML so you can embed assets directly in WPF/UWP/WinUI workflows. It helps avoid runtime SVG dependencies in .NET desktop stacks. Use it when your UI pipeline already consumes XAML resources. Dashed and dotted strokes are exported with XAML dash styles, with SVG dash values normalized relative to the stroke thickness as required by XAML.
SVG Symbol This wraps icon geometry in a <symbol>-based structure for sprite systems and reusable icon registries. It is useful for web apps that reference icons repeatedly through <use> without duplicating path data. This improves consistency and can reduce final HTML size.
VueTS Generates a Vue-friendly TypeScript component template so icons can be dropped into Vue codebases with minimal adaptation. It accelerates integration in component libraries and design systems. Teams can standardize icon props and styling conventions around this output.
ReactTS Generates React TypeScript component code suitable for modern React application stacks. It is useful for direct import into component folders, shared UI kits, or mono-repo packages. Developers can immediately wire class names, props, and theming behavior in familiar React patterns.
C++ Produces C++ vector path data for native pipelines where icons are constructed programmatically. It is useful when assets are embedded directly in binaries or rendered through custom engines. This target is a good fit for low-level UI frameworks and tooling code.
WPF Geometry Generates compact geometry path data optimized for geometry-based rendering in WPF. It is useful when your icon system relies on Geometry objects instead of full XAML trees. This can simplify resource usage in highly dynamic desktop interfaces.
VectorDrawable Generates Android VectorDrawable XML output, including path geometry and paint attributes. It integrates directly with Android resource systems and avoids shipping raster variants for each density. Use it for native Android apps that expect res/drawable vector assets.
SwiftUI Generates SwiftUI drawing code that can be embedded in Shape/Path-based UI components. It is useful for Apple-platform apps that build icon rendering in native SwiftUI view hierarchies. This target enables code-level customization while keeping geometry sourced from the same icon document.
MCP Automation and AI Integration
IconVectors 2.20 exposes 170 canonical underscore-named tools through the local MCP server, including the Editor, Explorer and batch PNG/ICO export, exact-color replacement, SVG versions, color adjustments, SVG optimization, currentColor conversion, centering/fitting, rotation/flipping, stroke outlining, per-paint automatic gradients, badge overlays and reusable Styles (2.20+). This is useful when you want an agent to create shapes, edit paths, inspect the current DOM, reuse palettes, render previews, navigate SVG folders, run safe batch starter operations, or export framework-specific code while preserving IconVectors’ own document model, rendering rules, and documented Undo behavior.
The integration is split into two processes:
IconVectors.exeowns the document, UI state, undo stack, and local bridge.IconVectorsMcp.exespeaks MCP over stdio and forwards tool calls to the running editor.
Typical MCP-driven workflows include:
creating and editing SVG vector icons from natural-language instructions,
inspecting element structure before applying changes,
analyzing imported or AI-generated icons through
document_analyzeCleanupSvgbefore export,applying same-tone fill or stroke gradients through
paint_autoGradient,generating code targets through
code_get,exporting assets through the same export pipeline as the UI,
automating repetitive palette, badge, or layout operations.
See also:
Exporting Icons
To save your work in formats suitable for deployment, you can use various export commands from the menu.
Export Minified
- Shift+Ctrl+M
Saves the icon in SVG format with:
Fewer decimals
No comments, spacing, or newlines
Optimized for smallest possible file size
Export to XAML
- Shift+Ctrl+X
Converts your drawing to Microsoft’s XAML vector format, ideal for use in WPF or UWP applications.
Export to Bitmap
- Ctrl+F3
Allows you to export the icon as a raster image in formats such as:
PNG - 32BPP RGB/Alpha Channel
Windows BMP - 32BPP RGB/Alpha Channel
Windows BMP - 24BPP Flat RGB Transparency
GIF - 8BPP Flat Indexed Transparency
JPEG - 24BPP Flat RGB
PCX - 24BPP Flat RGB
PNM - 24BPP Flat RGB
TGA - 32BPP RGB/Alpha Channel
TIFF - 32BPP RGB/Alpha Channel
XPM - 24BPP Flat RGB
You can adjust:
Output size in pixels or %
Background color and transparency
File format
Hint
When you select bitmaps without Alpha Channel, you need to specify a background/transparency color. Matt color is used in GIF to create smooth borders.
Export to Multiple Bitmaps
- Shift+Ctrl+F3
Need multiple versions of the same icon in different sizes or formats? Use this command to export a batch of icons with custom scale settings:
Select the target folder on the left
Define the base filename
Choose output sizes (e.g. 1x, 2x, 3x) or custom resolutions
Select formats (PNG, ICO, ICNS, etc.)
Icons are generated automatically into the selected folder
To create a subfolder, select its parent on the left and click New Folder.
You can select a real drive or filesystem root, such as D:\, if you have
permission to create folders there. The virtual Computer/Sections entry is not
a filesystem folder and cannot contain new folders.
The proposed name is New folder (numbered if that name is already taken).
Type a name or keep the proposal and press Enter to create the folder and
use it as the export destination. Press Esc during this initial edit to
cancel: the provisional row disappears and no folder is created. Escape during
an existing folder’s rename only cancels that rename; it never deletes the folder.
Cancelling the export does not remove folders whose creation you already confirmed.
Folder arrows are populated lazily for fast browsing: an unopened folder may
show an arrow even when it is empty; expanding it updates the arrow.
The available bitmap file formats are:
PNG Icons (PNG) - 32BPP Alpha Channel Transparency
Windows BMP Icons (BMP) - 32BPP Alpha Channel Transparency
Windows BMP Icons (BMP) - 24BPP Flat RGB Transparency
JPEG Icons (JPG) - 24BPP Flat RGB
Windows Icons (ICO)
Mac OSX Icons (ICNS) - Selected sizes
Hint
When you select bitmaps without Alpha Channel, you need to specify a background/transparency color. Matt color is used in GIF to create smooth borders.
Batch PNG and ICO from Explorer
To export several saved SVG files, select them in Explorer and choose . Choose PNG, ICO or both, their pixel sizes, an output folder and an optional filename suffix. PNG produces a file for each size; ICO produces one multi-size 32-bit file per source. The outputs have transparent backgrounds and leave the source SVGs unchanged.
Review the planned destinations before confirming. Save or exclude a selected source with unsaved Editor changes first. Existing outputs are protected unless you explicitly enable replacement. See Batch export to PNG and ICO (2.10+) for size limits, supported SVG inputs, naming and recovery behavior.
MCP offers explorer_batch_export_icons for this plan/apply workflow. To
export only the active Editor document as a single- or multi-size ICO, use
export with format:"ico" and a sizes list; see
Exporting Windows ICO files (2.10+). Neither export route adds an Editor Undo entry.
Batch SVG versions and color adjustments
Explorer also provides Make Icon Versions for separate Hot, Disabled and
Dark Theme SVG copies, and Adjust Icon Colors for one reviewed color
adjustment across saved source SVGs. They reuse the Icon-menu color engine and
the existing batch preview and recovery safeguards. See
Make Hot, Disabled and Dark Theme SVG versions (2.10+) and Adjust colors across SVG icons (2.10+) for
options, source-preservation versus source-modification behavior, and limitations.
The corresponding MCP tools are explorer_batch_make_icon_versions and
explorer_batch_adjust_colors; both plan before applying filesystem writes.
Optimized and theme-aware SVG sources
Explorer’s Optimize SVG Files previews file-size savings from conservative formatting, hexadecimal paint and path-number compaction. Path-coordinate rounding is optional and can change appearance; only smaller results are written. Metadata, license comments, references and significant text are preserved. See Optimizing SVG files (2.10+).
Convert to currentColor converts all supported solid colors or one detected
RGB in fills/strokes, while preserving effective alpha and untouched resources.
Authored color is retained with a warning when it limits theme inheritance.
See Converting paints to currentColor (2.10+) for supported inputs and preview behavior.
Both modify source files after review and have no Editor Undo. Their MCP tools
are explorer_batch_optimize_svg_files and
explorer_batch_convert_to_current_color.
Geometry variants without canvas changes
Explorer’s Center and Fit centers supported painted artwork or fits it proportionally inside equal SVG-unit margins. Stroke-inclusive bounds are conservative, so this is not optical centering; fitting scales strokes too. Rotate / Flip applies exact 90° left/right or 180° rotations, custom signed decimal angles, or horizontal/vertical mirrors about the existing canvas center. Custom angles are positive clockwise, negative counterclockwise; full turns wrap modulo 360. Canvas dimensions remain unchanged; custom rotation may clip artwork even on square canvases.
Both offer reviewed changes to originals or protected SVG copies with explicit
destinations and suffixes. Neither has Editor Undo. Unsupported inputs remain
untouched and are reported; source paths, metadata, definitions and symbolic
paints are not flattened away to force success. See
Centering and fitting artwork (2.10+), Rotating and flipping artwork (2.10+) and
Geometry output, review and limits for the exact boundary. The matching tools
are explorer_batch_center_fit and explorer_batch_rotate_flip, with
separate plan/apply calls; see Centering, fitting, rotating and flipping SVG files.
Batch base/overlay combinations
Use Add Badge Overlays to create one editable SVG for every combination of selected base icons and explicitly added overlay files. Set a nine-position anchor, proportional overlay size, edge margin and optional geometric badge cutout, then review each planned pair and destination. Output names use the base name and an editable per-overlay suffix. Source bases and overlays remain unchanged; outputs are not part of Editor Undo.
Preview and apply share immutable source checks, output-collision protection,
staging and rollback. Unsupported combinations are reported rather than silently
skipped or flattened. The corresponding MCP tool is
explorer_batch_overlay_icons. See Add badge overlays (2.10+) for
the options and safety boundary.
Clipboard Support
In addition to saving and exporting, you can copy the icon’s code to the clipboard in various formats, including:
Full or minified SVG
XAML
WPF Geometry / VectorDrawable / SwiftUI
React JSX or Vue template format
Clipboard-related commands:
- Ctrl+C
- Ctrl+V
- Shift+Ctrl+C
This makes it easy to paste icons directly into your app code, UI components, or markup.
IDE and Tool Integration
Axialis IconVectors works smoothly with modern development tools, thanks to standard file formats and clipboard-friendly code. You can:
Copy/paste SVG code into editors like Visual Studio, VS Code, or WebStorm
Open or edit icons that originated from Adobe Illustrator, Figma, or Inkscape
Drag icons between IconVectors and other apps or file explorers