Quiver's Arrow 1.1 builds editable SVGs from raw code

Anyone who has tried turning an AI-generated image into an SVG knows the pain: open the file in Illustrator, and you are greeted by an unholy mess of ten thousand fragmented paths and anchor points. Adjusting a single curve feels like performing surgery.

Quiver is taking direct aim at that mess. On April 16, the team rolled out Arrow 1.1 and Arrow 1.1 Max, bringing a cleaner, code-first approach to text-to-SVG vector generation.

Designing with code, not pixel tracing

Most vector tools work backwards. They generate raster pixels first, then try to trace outlines into vector contours. The result looks decent at a distance, but the underlying file is an uneditable nightmare.

Arrow was built around a different philosophy: vectors should be deliberately generated through code, not approximated from pixels. Instead of blindly matching raster surfaces, the model acts like a human designer, deliberately placing control points, defining shapes, and tuning gradients.

With Arrow 1.1, that distinction gets much sharper. The model significantly cuts back on messy, tangled paths and leans heavily into clean geometric primitives—basic shapes, clean lines, and actual editable text.

Because the resulting files are structured cleanly, you can inspect, scale, and tweak them without breaking the entire graphic. Layouts are better balanced, colors feel more intentional, and prompt adherence is noticeably tighter even with short, minimal inputs.

Cheaper runs and a precision-first Max tier

Quiver also tackled the production bill. Generating SVGs from text is now 33.3% cheaper, while vectorizing existing raster assets costs 50% less.

That makes a real difference for product teams generating hundreds of app icons, batch-processing marketing visuals, or exploring dozens of logo variations in a single sitting.

For enterprise workflows where millimeter-level precision matters, Quiver introduced Arrow 1.1 Max. It uses the same foundation but spends more compute on structural alignment, tighter tolerances, and color preservation.

Arrow 1.1 Max is tailored for technical diagrams and complex illustrations where small geometric blips would otherwise require manual cleanup. The tradeoff is predictable: higher latency and higher cost per run.

Why it matters

For UI designers and frontend developers, Arrow 1.1 crosses the threshold from novelty to production utility. It delivers actual code assets you can check into a Git repo or paste directly into Figma, rather than disposable visual mockups.

Most frontier image models are obsessed with photorealism and pixel density. But software interfaces, branding kits, and digital products run on vectors. By treating vector creation as a pure code generation problem, Quiver avoids the bloat of raster conversion altogether.

We think this is a genuinely smart architectural bet. While handling deeply nested interactive vector components may still pose challenges down the road, Quiver is building the right foundation: SVGs that developers and designers can actually edit.