u/tamingunicorn

a few weeks ago I posted PerfectVector, the image-to-vector SaaS I'm building on Reddit.
[https://www.reddit.com/r/SideProject/comments/1uqi6ay/i\\\_spent\\\_6\\\_months\\\_training\\\_a\\\_model\\\_to\\\_vectorize\\\_ai/\](https://www.reddit.com/r/SideProject/comments/1uqi6ay/i\_spent\_6\_months\_training\_a\_model\_to\_vectorize\_ai/)
traffic jumped fast that we stopped celebrating and started watching the GPU queue.

a vectorization job normally takes around 10 seconds. during the spike, some took more than 2 minutes. we spent a lot of time working on capacity and queueing, but the GPU bill was already higher than the revenue coming from those users.

the pricing problem was separate, but it made the economics worse. we were giving new accounts 10 download credits plus another free daily credit. people used the product, but for a few weeks nobody new paid for it.

last week we cut the free download allowance to 5 credits. since then we've had a few new subscriptions and pay-as-you-go purchases after weeks of zero.

I don't know yet if the pricing change caused that. existing users still have old credits to burn, and one week is nowhere near enough data.

mostly recording this because it was a strange lesson: the marketing worked, but it made the product slower and the business more expensive to run. getting traffic was only useful after we started fixing the economics and the GPU bottleneck behind it.

a few weeks ago I posted PerfectVector, the image-to-vector SaaS I'm building on Reddit.
https://www.reddit.com/r/SideProject/comments/1uqi6ay/i_spent_6_months_training_a_model_to_vectorize_ai/
traffic jumped fast that we stopped celebrating and started watching the GPU queue.

a vectorization job normally takes around 10 seconds. during the spike, some took more than 2 minutes. we spent a lot of time working on capacity and queueing, but the GPU bill was already higher than the revenue coming from those users.

the pricing problem was separate, but it made the economics worse. we were giving new accounts 10 download credits plus another free daily credit. people used the product, but for a few weeks nobody new paid for it.

last week we cut the free download allowance to 5 credits. since then we've had a few new subscriptions and pay-as-you-go purchases after weeks of zero.

I don't know yet if the pricing change caused that. existing users still have old credits to burn, and one week is nowhere near enough data.

mostly recording this because it was a strange lesson: the marketing worked, but it made the product slower and the business more expensive to run. getting traffic was only useful after we started fixing the economics and the GPU bottleneck behind it.

if image trace gives you a "vector" with a couple thousand nodes on a shape that should have forty, that's not your settings, it's just what auto-trace does. it follows the boundary between colors in your raster and drops an anchor point along every little wobble. the wobble is anti-aliasing, the band of soft semi-transparent pixels on every edge that makes it look smooth on screen. the tracer reads that fuzz as a jagged line and faithfully traces all of it.

I ran a pretty simple owl illustration through it recently and got 522 nodes where a clean version of the same art is about 59. it's miserable to edit, every node is a handle in your way, and it's worse if the file's going to a cutter since the machine stutters along every micro-segment.

Object > Path > Simplify after tracing helps, just know it's destructive and softens corners. turning the trace settings down before you trace helps too but you lose real detail with the junk. honestly the bigger fix is upstream, a flat hard-edged source traces way cleaner than a soft ai render or a compressed jpg.

if illustrator beachballs every time you nudge something, it's almost never that file is "too big", it's usually one of a few specific things choking the render. worth knowing what to look for before you blame your machine.

the most common one is placed raster images, especially high-res ones you embedded instead of linked. illustrator re-renders them on a lot of operations. Window > Document Info > Objects (and Linked Images) shows what's actually in the file. link the heavy stuff, embed only what you need.

second is live effects stacked up, drop shadows, feathers, glows. each one recomputes every time you touch the art. once an effect is final, select it and Object > Expand Appearance so it stops recalculating.

third is a monster path from a trace, tens of thousands of points on one shape. select all, check the point count in Document Info, and Object > Path > Simplify the worst ones.

last, check Effect > Document Raster Effects Settings. if that's at 300ppi on a screen-only file, it'll crawl on its own. drop it while you work.

if you trace a line drawing in Trace Bitmap and every line comes out as two cuts on the laser/cricut, it's not your machine. the default trace outlines your shapes, so a single pen stroke becomes a skinny filled rectangle and the machine cuts down both long edges. that's your double line.

the fix is centerline mode. trace bitmap has a centerline option that lays one path down the middle of the stroke instead of tracing both sides. for line art and lettering that's what you actually want. the default Brightness/Colors modes are outline tracers, so they'll always give you the two-edge result on thin strokes.

two other things fake the same symptom: a shape with both a fill and a visible stroke reads as two cuts (kill one of them), and stacked duplicate paths from a marketplace file (ungroup, check the Objects panel, delete the copy).

centerline only helps on line and stroke art, not solid fills, but that's usually where the doubling bites anyway.

people keep asking why chatgpt or gemini can't vectorize their image, and it's not a prompt you're missing, these models just don't trace. a real svg is shapes drawn with math, your png is a grid of pixels, and converting one to the other needs an actual tracing algorithm, not a language model.

so chatgpt usually hands you one of the three things

a new png that looks cleaner but is still pixels, or an .svg with your raster just imbedded inside it, or real svg code that's two thousand unusable nodes. gemini's the confusing one, it can genuinely write svg from a text prompt because svg is just cml, but upload an actual image and it just redraws a rough guess of what it thinks it sees. it's not reading your pixels.

quick way to check a "vector" you got: zoom in (crisp = real, blurry = fake), and try to select one shape on its own. if the whole thing is one locked image, or it's thousands of nodes, nothing actually got traced.

easiest fix is boring, just run the png through a real tracer (illustrator image trace, inkscape trace bitmap) and check it after. ai/ml background here and it still feels weird to me that the model writing perfect code can't trace a clean circle.