Extensions have the downside that a malicious actor can buy out the original dev and start using them as an intrusion point.

It's possible to run WebAssembly programs from the command line (without any GUI) using WASI (see e.g. https://github.com/WebAssembly/WASI). Thus if the user downloads pdfconverter.wasi , and the user already has e.g. wasmtime installed, they can run `wasmtime pdfconverter.wasi input.pdf output.pdf` from the command line (see https://github.com/bytecodealliance/wasmtime/blob/main/docs/... for details).

In addition to the web site, the Electron app and the Chrome extension, you may want to distribute a command-line version of your tools as WASI-style .wasm program files. If you do so, I would exclusively use the them this way, from the command line.

Don’t make either unless you have the resources to support them. Anything paid is also a business process with tax implications.

Local-only web apps are great one-off projects, but extensions and native apps require much more maintenance.

Make the Desktop Version natively, even tho its time efficient to make it just Electron