About SVGFlow
SVGFlow is a set of small, single-purpose SVG tools that run entirely in the browser. Open a file, do one job to it, take it out again. There is no account, no upload, and no server-side processing of any kind.
Why it exists
Most online SVG utilities post your file to a server to do work the browser can already do natively. That trade is a bad one twice over. It means a design file — often unreleased brand work — sits in someone else's logs for an unknown period, and it means a round trip and a queue for an operation that should be instant.
Every tool here is built on three APIs that have shipped in every browser for years: FileReader to read the file, DOMParser to parse it, and canvas to rasterise. Once the page has loaded, the network is not involved again. You can open the network tab and watch nothing happen, or disconnect entirely and keep working.
What it deliberately does not do
The tools are narrow on purpose, and each one documents its own limits on its page. The optimizer will not merge paths or convert shapes to paths, because those are the passes where an optimizer starts changing how a file renders. The editor draws shapes and bezier paths, edits anchors and runs the basic booleans, but has no brushes, effects or gradient meshes — it is for changing a file someone handed you, or building a simple one, not for illustration work. The tracer cannot recover text as text, and says so rather than producing a shape that looks like a word.
Where a tool cannot do something, the page says which tool or which approach can. That is more useful than an option that quietly produces a worse file.
How the guides are written
The guides cover problems that come up while using the tools — why a fill will not change, where 40 KB of an icon actually goes, which favicon files a browser still asks for. They are written from working with these files rather than assembled from other articles, they name the cases where the advice stops applying, and they are dated and revised when browser behaviour moves. Nothing in them is placed or sponsored.
How it's funded
Advertising, through Google AdSense. Ad slots are fixed-size containers placed outside the working area — never over the canvas, never between a control and its result, and never styled to resemble a button or a result panel. The height is reserved before the ad loads so nothing on the page moves under your cursor. If an ad ever looks like part of the interface, that is a bug; report it and it will be moved.
No tool is gated, there is no paid tier, and no feature is withheld to sell later. What your browser can do, the site lets it do.
Who makes it
SVGFlow is an independent project, built and maintained by one front-end developer working on it in spare hours since 2024. It is not backed by a company and has no team behind it, which is the honest reason some things take a while.
Bug reports, files that will not open, and ad complaints all reach the same inbox: bytefusionalgos@gmail.com, or through the contact page. A broken file attached to the message is worth more than any description of it.