Vectr

Vector editors mostly assume you want depth, and present a workspace built for somebody who already knows what a bezier handle does. Vectr assumes the opposite, offering a small set of tools aimed at people making a logo or an icon rather than an illustration.

Shapes, a pen tool, text, layers, the basic path operations cover what Vectr does. There is no library of effects to explore and no vocabulary to learn first.

Where the work is pixels rather than paths, a raster editor built for photographs and painted images is the counterpart for that entirely different job.

The one thing it has that its serious rivals do not is the reason to look at it, and it has nothing to do with drawing.

Anybody with the link can watch you work

Sharing a Vectr document produces an address, and whoever opens it sees the drawing live as you change it.

That is properly unusual in this category. Sending a colleague a link and having them watch the logo change while you discuss it on the phone removes the export, attach, wait, reply cycle entirely, and desktop vector editors have never offered anything comparable.

Editing together works the same way, with more than one person changing the same document at once.

The mechanism is the link itself, which is also the access control. Anybody holding it has whatever access the link grants, so a document address forwarded on is a document shared onward, and there is no second check behind it.

The same document in a browser or an application

Vectr work continues wherever you open it, since the document lives on the service rather than on your machine.

That is convenient in the ordinary way, meaning starting something on one computer and finishing on another without carrying a file.

It also means your work is stored on somebody else’s infrastructure by default rather than as an option, which matters more here than it would for a maintained service, for reasons the next section covers.

A quiet cloud service is a different risk

Here is the honest Vectr consideration, and it separates this from an abandoned desktop program.

Development has been quiet for a long time. For a desktop application that means no new features and files that continue to open, since they sit on your own disk and the program still runs.

For a service holding your documents, quiet development raises a different question. If the service eventually stops, the documents stored there go with it, and nothing on your machine takes their place.

The practical response is straightforward. Export what matters as you go rather than leaving finished work in an account, so the drawings exist as files you hold regardless of what happens to the service.

Where the ceiling is

The simplicity that makes Vectr approachable is also where it stops, and the boundary arrives sooner than beginners expect.

Boolean operations for building shapes by combining simpler ones, proper node editing with different node types, path effects, tracing an image into paths and anything resembling a professional export pipeline are outside what it offers.

Most people meet that ceiling on their second or third real project, which is the point at which learning a fuller application becomes the better investment. Inkscape covers all of it, works on files kept on your own disk, and asks considerably more patience at the start.

Conclusion

Vectr does two things well. It lets somebody who has never used a vector editor produce a usable logo in an afternoon, and it lets another person watch that happen from a link, which nothing on the desktop offers.

Weigh where the work lives before committing anything important to it. Documents sit on a service whose development has been quiet, the sharing link is the only gate in front of them, and the tool set runs out on the second real project. Export as you go, treat it as the approachable starting point it is, and move to a fuller application when the ceiling arrives.