Start an SVG edit by deciding whether you need a new visual interpretation or an exact source change. AI refinement is useful for describing an appearance change. A specific hex color, path coordinate or accessible label is often clearer to change directly in SVG code. Keep the original file before either operation.
Use the AI SVG Generator to create an initial design, then open its Edit action to describe a refinement. For a broader walkthrough from idea to finished file, read the AI SVG Generator complete guide.
For this example, we created a shield-and-leaf symbol for the fictional brand FlowMint, then used Classic to refine it in SVG AI. The original design has a mint leaf inside a navy shield. We entered this edit request:
Change only the mint green fill of the leaf to warm orange. Keep the navy shield, navy leaf veins, composition, shape and size unchanged.


The leaf turned orange, but the edit also shifted the navy, changed the curves and tightened the framing. Compare the whole design after an AI edit, including details you asked to keep.
| Version | Full file | Observed structure and change |
|---|---|---|
| Generated source | Original SVG | Three paths; square 2048-unit viewBox; navy rgb(5,36,72), mint rgb(133,211,171) |
| AI edit | AI-edited SVG | Three paths; orange rgb(251,142,52), navy rgb(5,39,76); changed paths and viewBox |
| Manual finish | Manually corrected SVG | Restored original navy and square viewBox/dimensions; retained AI-edited orange and geometry |
To finish this version, we changed the navy fill and viewBox directly in the SVG code. The downloadable manual version keeps the AI-edited orange and curves. If you need to preserve every original curve, start from the original SVG and change only the leaf's fill value.
Use the edit history to compare versions, then choose Download SVG to save the one you want to keep. Sign up to get starter credits. SVG downloads require paid access through an eligible subscription or credit purchase.
Download the FlowMint project files for all three SVG versions, prompts, screenshots and a comparison page. The SVGs contain paths with no embedded raster image. Try the comparison page on light and dark backgrounds: the navy shield is clear on white but loses contrast on a dark surface. A lighter shield would be a useful separate version for dark interfaces.
For a precise color change, edit the SVG source directly. This hand-coded envelope example includes three complete files with identical geometry, so you can see exactly what each edit does.
| Version | Download | Exact change |
|---|---|---|
| v1 | Coral source SVG | Starting envelope with a coral outline |
| v2 | Manual color edit | Stroke changed from #fb7185 to #0f766e |
| v3 | Manual final SVG | Added title, description and standalone image semantics |
Open the source in a text editor and replace #fb7185 with #0f766e. That changes the outline from coral to teal while keeping the envelope's shape. The final version also adds a title and description for standalone image use.
The complete final source is:
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" width="24" height="24" role="img" aria-labelledby="mail-title mail-desc">
<title id="mail-title">Message</title>
<desc id="mail-desc">An envelope drawn with a teal outline.</desc>
<g fill="none" stroke="#0f766e" stroke-width="1.8" stroke-linecap="round" stroke-linejoin="round">
<rect x="3" y="5" width="18" height="14" rx="2"/>
<path d="M3.8 6.2 12 12.5 20.2 6.2"/>
</g>
</svg>
Each file has one foreground rectangle and one path, a 24 × 24 viewBox, and no embedded raster image, external resource or font dependency. The final file adds a title and description rather than converting visible lettering. The displayed teal is held constant on a dark background: choose and review a separate contrasting theme variant when your design needs one.
For a full review package, download the handoff archive. Its local review page shows all three versions at 24, 48 and 128 CSS pixels, with light and dark backgrounds. The workflow guide explains how to keep its brief, feedback record and delivered version together.
For an existing generated design, save the original, open Edit, and enter one focused instruction. For example: “Change the envelope outline to teal, preserving the envelope shape and transparent background.” Review the displayed credit cost before submitting the edit.
After an AI edit, compare the appearance and SVG code with the source. Similar-looking outlines can use different paths. Save any later code changes as a separate manual version so you can return to either stage.
Keep the prompt beside each saved version. It makes the history easier to follow when you return to the project or share it with a designer.
An AI result may need unwanted details removed; a converted image may need tracing artifacts cleaned up; a manually drawn SVG may need alignment corrections. Inspect the file and identify the problem before choosing an editor.
Write the actual requirements: intended size, background, exact palette, file-size budget and embedding method. A file can look correct in a large preview yet fail in a small button. Avoid universal byte limits; choose a budget appropriate to the application and asset complexity.
Preserve the source, submit one focused appearance change, and save the new result. Note the model and settings so you can continue the work later. Compare lettering, spacing and silhouette as well as the requested change.
Look for stray paths, unwanted background regions and excessive detail. If the file contains an embedded image, path edits cannot change pixels inside it. The photo-to-SVG guide explains how to prepare the source image and choose a conversion approach.
Duplicate the source before moving nodes or changing styling. Make one category of change at a time: geometry, palette, then metadata. The downloadable envelope demonstrates exact palette and metadata changes; it does not need node simplification.
Inspect the source geometry before moving a point. In this example, M3.8 6.2 12 12.5 20.2 6.2 draws the envelope flap with straight segments. Moving its middle point changes the flap depth. Save that as another version and compare it at 24px; do not mix it into the color-only edit.
Inspect fill, stroke, inherited group styling and gradient stops. For the envelope, changing the group's stroke updates both visible shapes. An embedded raster image or CSS rule can complicate a global color replacement, so verify what actually renders afterward.
Check padding within the viewBox, not only the element's width and height. The envelope spans x=3 to x=21 before the stroke extends beyond those coordinates. Include stroke extents when checking clipping and optical balance.
Keep source, AI result and manual final as separate files. Preserve the prompt and reason for each step. A version history in the app is useful when available, but your delivery package should identify the exact file being handed off.
Optimization changes representation to reduce size or complexity. Compare appearance after any such change, especially gradients, masks, IDs and accessibility metadata. Do not remove title/description elements by habit when the embedding uses them.
Filters, masks and clipping paths can change both appearance and bounds. Test their rendered edges at the intended size. Avoid adding an effect simply to hide poor geometry; it can introduce another compatibility problem.
Keep a useful viewBox and test actual CSS dimensions. A viewBox makes scaling possible; it does not make every detail readable at every size. Draw a separate small-size variant if simplifying the large illustration would harm its main use.
Test the embedding method your site will use. In an external img, an SVG does not inherit the page's currentColor. An inline SVG can inherit styling, but repeated instances must avoid conflicting IDs.
Confirm dimensions, color requirements and accepted file formats with your print provider. Request a proof when color or small detail is critical, and keep the editable source for any adjustments they recommend.
Decide whether the image is informative or decorative in context. A button with its own accessible name normally uses an empty image alt attribute to avoid repeating the label. A standalone informative image needs useful alternative text; inline title/description IDs must be unique in the document.
Check unsupported effects, missing fonts, external resources and inherited CSS. Open the same file in each browser your project supports, using the same page styling and display size.
Compare path counts and look for embedded image data or added metadata. Save the unmodified edit before cleanup. A larger result may still be appropriate; use the project's size budget and visible quality to decide.
View the image at 100% zoom and its intended CSS size. Increase optical weight or remove small secondary details in a separate version. The thin-stroke diagnostic shows why a large preview can conceal this failure.
Compare the actual paint values and their rendered context. Replace exact hex values directly when required. Test transparency over more than a white background; a hidden background shape can change the appearance in production.
Check the subject and unwanted content first, then inspect the paths. AI refinement can redraw parts of the image. Use direct source edits when the original nodes or exact geometry must stay fixed.
Inspect raster content, isolated tracing fragments and edge noise. Keep the original reference alongside the SVG so that simplification can be judged against the intended fidelity. Do not infer vector editability from the filename alone.
Preserve useful groups and IDs, especially when other code references them. Review geometry changes before formatting or cleanup so a meaningful diff stays readable. See custom SVG image creation for planning original geometry.
Choose the smallest change that addresses the requirement. Preserve a known-good version. Stop when the acceptance criteria pass instead of adding decorative changes unrelated to the brief.
Learn your editor's shortcuts for duplicate, undo, zoom-to-selection and save-as. These are useful when comparing versions and checking small geometry changes. Shortcut mappings vary by application and operating system.
Work until the file meets its intended size, palette and delivery requirements. A single color change may need little cleanup; a dense illustration with lettering and clipping paths needs a more detailed review.
Yes. Plain SVG markup can be edited in a text editor, and vector-editing tools offer visual controls. The right choice depends on whether you need exact code changes or interactive geometry work. Review any tool's current terms before adopting it.
Editing changes content or appearance. Optimization aims to reduce representation cost while preserving the required result. The two can overlap, so compare before and after rather than relying on the operation's name.
Work on a duplicate and compare curves at the intended size and an enlarged detail view. Preserve corners and silhouette features that communicate the subject. A lower path count alone is not a quality improvement.
Keep editable text in your source when future wording changes matter. An outlined delivery variant can remove a font-rendering dependency, but it loses ordinary text editability and search/select behavior. Confirm the font's license and keep an accessible label where needed.
Confirm permission, preserve the original and understand the layer/ID structure before changing it. Record your modifications. Never use a customer file as a public example without authorization.
SVG AI lets you describe a refinement in natural language and compare versions in the edit history. Use it for changes in appearance, then use a vector or text editor when you need precise control over individual nodes, colors or SVG attributes.
Save at meaningful boundaries: original, each AI result, geometry changes, palette changes and final delivery. Keep the final file's review record so another person can identify the approved version.
Preserve the source, distinguish generated refinements from exact manual changes, and verify the file where it will be used. The SVG Generator starts the creation task; careful file review completes the editing task.