Disclosure: This draft was generated with AI and checked against the cited primary sources, with a separate AI editorial review. It was prepared for the FrameSprite team, which has a commercial interest in FrameSprite. Proposed examples are not executed tests unless explicitly identified as recorded fixture results.
An imported SVG may contain vector shapes rather than a paintable pixel layer. Use shape tools for geometry changes, or rasterize a duplicate at the intended output size before making pixel repairs. Repeatedly unlocking the layer will not turn its shape representation into ordinary brush pixels.
Key Takeaways
- Determine whether you need an editable SVG, a raster game icon or both.
- Make shape-level changes before rasterization when they must survive later resizing.
- Retain the original vector source and judge repairs at the actual delivered dimensions.
Check the layer type before changing tools
Open the layer tree and identify the imported object's representation. Krita's Vector Layers reference describes SVG import and shape organization. A vector layer also has its own shape order, so a detail can be present but hidden behind another shape within the same layer.
Use the Shape Selection tool to select the icon's relevant shapes. If the change is a misplaced gem, wrong shield proportion or an extra contour, edit that geometry directly. A painted patch over an incorrect vector contour may look acceptable at one size but leave the underlying source wrong.
This diagnosis does not cover an imported File Layer, which has another reference and editing model. The Layers and Masks overview helps distinguish those layer types. Choose a repair based on the actual type, not on the filename you originally dragged into the editor.
Decide where vector editing should end
For a game shipping SVG icons, keep the repair in supported vector features and inspect the real SVG consumer. Raster paint added above a vector layer becomes another delivery dependency if you expect a self-contained vector asset. Do not promise a pure-vector result after adding raster-only detail.
For a game shipping PNGs, preserve the vector master and make a duplicate raster working version at the final size. Use the layer conversion command appropriate to the installed Krita version, then confirm the result is a paint layer before brushing. Record the rasterization size; converting at an arbitrary oversized canvas and shrinking later changes the pixel decision you are trying to make.
Repair one ambiguous detail at its real size
Take an unexecuted example: a shield icon contains a narrow notch that looks clear in a large SVG but collapses at 32 pixels. First inspect whether the notch's vector geometry needs widening. If the icon will only ship as a 32-pixel PNG, a small raster adjustment may be the intended final art direction. If several resolutions must remain editable, correct the geometry and rasterize each size deliberately.
| Required output | Preferred repair level | Retain |
|---|---|---|
| Editable SVG family | Shapes and paths | Vector master and dependencies |
| One fixed PNG size | Geometry, then target-size pixels | Vector source plus raster repair copy |
| Multiple PNG sizes | Shared geometry with reviewed exports | Each size's acceptance comparison |
Reopen each exported PNG and inspect the notch, outer alpha edge and alignment in its game slot. Do not accept a repair solely from the zoomed-in working canvas. A clean raster icon can legitimately have fewer visible details than its vector master.
Related checks include SVG tracing detail loss, portable SVG dependencies and DPI versus pixel dimensions. No Krita conversion or target-game render was executed here.
Written by the FrameSprite Workflow Team. Report a correction.
Top comments (0)