

Decide whether the job needs a bold raster image or true editable vector geometry. Those outputs can look similar in a small preview. A vector-inspired image treatment does not by itself supply SVG paths, named objects or a scalable production master.
Choose and record the source
Identify the source scene in large bands: water, quay, trees, low buildings and skyline. Record which relationships must survive and which fine details may be removed. If signage, railings or people provide essential factual information, a highly simplified treatment may be unsuitable for that use. Do not assume that an omitted feature can be recovered by enlarging the output.
Make the central decision explicit
Compare the candidate in two passes. First check band order, silhouette and horizon placement. Then judge the palette and the balance of occupied and quiet areas. Flat color can be useful even when it is not a faithful local color record, but that choice needs approval. A source showing blue water does not prove that an intensely pink interpretation documents its real appearance.
Inspect the actual handoff
Inspect the actual file in the application that will receive it. For a raster, check pixel dimensions and intended display size. For a promised vector handoff, inspect real paths and editability rather than only the extension. If tracing or reconstruction is needed, treat it as a separate external production step and review the altered shapes after conversion.
Can I scale the result indefinitely?
Do not promise that for a raster. Confirm the actual asset structure and the destination requirements. A larger file or smooth preview is not evidence of resolution-independent shapes.
Preserve the shoreline with a shape budget
Choose a hypothetical waterfront with a tower, three roof groups and a sloping shoreline. Rank the tower and shoreline as essential, then allow minor windows and reflections to collapse into larger fields. A shape budget is a design constraint rather than a feature claim: decide which groups may merge and which must remain separated before judging the output.
Compare the result as a small silhouette first. If the tower blends into a neighboring roof, a larger file will not repair the lost hierarchy. Next inspect the water-land boundary and compare the order of the major buildings against the source. Only then evaluate the limited palette. Keep a note of any deliberately omitted objects so later reviewers do not mistake them for accidental loss. If the handoff calls for scalable paths, specify a separate vector deliverable and inspect its paths in a vector application; a crisp raster preview is evidence of appearance alone.
Allocate waterfront shapes and inspect the delivered structure
For the hypothetical waterfront, reserve separate major shapes for the tower, three roof groups, shoreline, water and sky. This seven-part budget is an editorial plan, not a software object count. Minor windows may disappear; the tower must remain distinct and the sloping shoreline must still separate land from water.
| Candidate result | Composition decision | File decision |
|---|---|---|
| Tower merges with the second roof group | Reject the shape hierarchy | More pixels will not restore that separation |
| Tower and shoreline survive in a flat PNG | Approve that raster appearance if the brief allows it | Do not promise independently selectable shapes |
| A requested SVG contains only one embedded bitmap | Appearance may match | Hold editable-path delivery; request reconstruction or a genuine path-based asset |
MDN's format guide distinguishes PNG raster data from SVG drawing commands and notes that SVG can also contain bitmaps. Therefore even an SVG filename is insufficient. Open the actual delivered file in a suitable vector application and inspect whether the expected shapes are paths. Keep the artwork approval separate from this editability check; this constructed example reports no tracing or export test.