Which export formats are available and which should I use for web vs print?
Use SVG for web and UI because it's scalable, editable, and styleable with CSS. Export PNGs (16–64px) for legacy thumbnails or places that require raster images. For print or advanced vector editing, export PDF or EPS to open in Illustrator or Sketch. The generator outputs grouped SVGs to simplify importing into design tools.
How do I add accessible labels and ARIA attributes to generated SVG icons?
Include a <title> and optionally a <desc> inside the SVG and give the SVG role="img". Example: <svg role="img" xmlns="http://www.w3.org/2000/svg"><title>AI chip</title><desc>Simple neural chip icon</desc>…</svg>. For decorative icons, use aria-hidden="true" and focusable="false" on the SVG element and ensure interactive controls have visible labels or aria-label attributes.
Can I customize stroke width, corner radii, and color palette after generation?
Yes. The generator produces editable SVGs with grouped elements and named layers so you can tweak stroke widths, corner radii, and colors in code or in vector editors like Figma and Illustrator. For global color changes, maintain a monochrome master or separate color layers.
What size and simplification should I use when creating a favicon or app icon?
Design favicons as simplified, single-shape marks optimized at 16–32px. Remove inner details and use bold counters. Export a single-color 16px and 32px PNG plus a single-color SVG master for best results.
How do I convert an SVG export into a React component or inline SVG in HTML?
For React: copy the inline SVG markup into a component file, replace attributes like stroke-width to camelCase (strokeWidth), remove or namespace IDs, and accept size/color props. For HTML: paste the inline SVG directly into the DOM and use CSS variables to control fill/stroke where appropriate.
Are generated symbols suitable for a design system and how should I version them?
Yes. Use the generator's grouped and named layers to keep a consistent tokenized set. Store a monochrome master and style variants, version via your design system repo (Git or Figma file history), and keep naming conventions consistent (e.g., ai-chip-24-outline, ai-chip-24-filled).
How to ensure sufficient color contrast for icons used over images or colored backgrounds?
Test icons at target sizes with the actual background. Use two-tone separation or semi-opaque backing where contrast is low. Prefer single-color high-contrast masters for small icons and use WCAG contrast checkers for larger iconography that conveys information.
Can I batch-generate icon sets with consistent visual rules and naming conventions?
Yes. Use prompt templates that specify style, stroke width, grid size, and naming patterns. The generator supports generating multiple variants in a single batch so you get consistent geometry and layer names across an icon set.
What are best practices for scaling icons without losing legibility?
Design on a consistent grid (24px or 32px), align strokes to pixel-friendly values for small sizes, and simplify paths for favicons. Provide separate variants for very small sizes rather than scaling down complex artwork.
Troubleshooting: my SVG has extra metadata or transforms — how to clean it for production?
Open the SVG in a text editor or vector tool and remove editor-specific metadata (comments, inkscape:sodipodi, sodipodi:namedview). Flatten unnecessary transforms by ungrouping and applying object transforms in the editor, then re-export. The generator already strips most metadata, but you can run SVGMin or SVGO as a final step.