Logoly: a browser-based logo generator for PornHub-style wordmarks

What Logoly actually generates, and who it is for

Logoly produces wordmarks in the visual style of two adult-site brands. The README lists four capabilities: generating a logo like PornHub or OnlyFans, downloading it as PNG or SVG, customising the logo colour, and customising the font size. That is the entire feature set. There is no shape library, no icon set, no layout grid, and no template gallery.

The audience follows from that scope. If you are making a joke site, a stream overlay, a thumbnail, or a mock brand for a design critique, Logoly gets you a file in a few clicks without opening Illustrator or Figma. If you are building an actual identity system, the tool stops well short: the README documents no way to load a custom typeface, and the TODO section still lists "customize fonts" as unbuilt. So the output is locked to whatever fonts ship with the app.

The project is also explicitly a web app rather than a library. There is no published package to import, and package.json marks the project "private": true, so it is not intended to be consumed as a dependency. You use the hosted site, or you run the source yourself.

The Vue 3, Vite and dom-to-image pipeline behind the export button

The stack is visible in package.json. The UI is Vue 3 with Vuetify 3 for components, Pinia for state, vue-router for routing, and @vueuse/core for composables. Tailwind 4 runs through @tailwindcss/postcss, and sass and stylus are both present as dev dependencies, which suggests the styling is layered rather than unified.

The interesting dependency is dom-to-image. That is what turns the rendered DOM node into a downloadable file, which explains why the README can promise both PNG and SVG from the same view. The logo you see on screen is a live DOM element, not a canvas drawing, and dom-to-image serialises it. This is a pragmatic choice: the preview and the export stay in sync because they are the same object. It also means export fidelity depends on the browser's rendering of that node, and on how dom-to-image handles any web fonts or external assets referenced inside it.

Build tooling is Vite 5 with @vitejs/plugin-vue and vite-plugin-vuetify, plus vite-plugin-compression. Linting and formatting go through Biome, with Prettier still listed as a dev dependency, and tests run on Vitest with coverage via both istanbul and v8 providers. The repository root also carries biome.json, .prettierrc.json, tailwind.config.js, postcss.config.js, vite.config.js, and vitest.setup.js, so the configuration is spread across the usual per-tool files.

Running Logoly locally with npm

The README states the requirements plainly: Node.js 18+ and npm 10+. It also states that npm is the official package manager and asks contributors not to submit other lockfiles, warning that Bun, pnpm, or yarn may create mismatched lockfiles and are not supported. Take that seriously, because the repository ships a package-lock.json.

Start by cloning the project and installing dependencies at the project root. The README gives npm install, with npm ci offered as the clean-install variant.

npm install

Next, start the development server. The README's step is npm run dev, which maps to vite in package.json.

npm run dev

Vite prints a local URL in the terminal. Opening it gives you the editor: a text box, colour and font-size controls, and an Export button, matching the four steps in the README's How to Use section.

When you want a production bundle, the README's final step is npm run build, which runs vite build. A preview server is also defined.

npm run build
npm run preview

The repository defines the rest of the toolchain as npm scripts too: format and lint and check and check:fix for Biome, and test for Vitest with coverage. The README does not document any environment variables, ports, or deployment configuration beyond the note that the hosted site is deployed on Vercel.

Where Logoly is the wrong tool

The clearest limitation is typographic. The README's TODO list still contains "customize fonts", and the feature list mentions colour and font size but never font family. If your wordmark needs a specific typeface, Logoly cannot produce it, and no amount of configuration will change that because the capability is not in the app.

The second limitation is the export path. Because rendering goes through dom-to-image against a live DOM node, the SVG you get is a serialisation of that node rather than a hand-authored vector file. The README does not document how the SVG is structured, whether text is converted to paths, or how the output behaves in a vector editor. Anyone who needs clean, editable paths for a print pipeline should verify the exported file in their own editor before committing to it.

The third is scope creep in the other direction. There is no project management, no version history, no team library, no brand kit. Logoly makes one file at a time. If you need a consistent set of marks across multiple products, this is a single-shot utility, not a system.

Finally, the README opens with a note that a new version is in active development on the new-vue3 branch. That is a signal about where effort is going. The default branch is master, and the last push to the repository was on 2026-07-06.

Logoly compared with a general vector editor

The natural alternative is not another logo generator but a vector editor such as Inkscape or Figma, or a general-purpose canvas library if you want to generate marks programmatically.

The difference is where the work happens. Logoly fixes the composition: the wordmark layout is decided by the app, and your inputs are text, colour, and size. A vector editor gives you the raw primitives and no opinions, which means you can match any typeface, adjust kerning, and export to whatever format the printer asks for. The cost is time and skill.

Logoly's advantage is the same as its constraint. Because the layout is fixed, the output is consistent and fast, and the README's four-step workflow is short enough to describe in a sentence. A vector editor has no such guarantee: two people using it will produce two different files.

If you want programmatic generation with control over typography, the closer comparison is a drawing library used directly in your own build, where you own the font loading and the export format. Logoly is the opposite trade: less control, less setup, and a working file in under a minute.

Licence and the cost of keeping a fork current

Logoly is released under WTFPL 2, per the LICENSE entry and the README's licence section. That is a permissive, do-what-you-want licence, and it is unusual enough that some organisations will want their legal team to look at the wording before shipping a fork. This is not legal advice; read the LICENSE file yourself.

On maintenance cost, the honest picture from the repository is mixed. The last push was on 2026-07-06, and the README states that a new version is in active development on the new-vue3 branch. That means the default master branch and the new-vue3 branch may diverge, and a fork based on master will not automatically receive the rewrite.

The dependency list is also a cost centre. Vue 3, Vuetify 3, Tailwind 4, Vite 5, Vitest 4, and Biome 1 are all version-pinned with caret ranges, and the project uses two coverage providers plus three styling systems (Tailwind, sass, stylus) and two formatting tools (Biome, Prettier). Upgrading any one of those in a fork means checking the others. There are no releases listed in the repository, so there is no tagged version to pin against; you track a branch.

Editorial conclusion

Logoly fits anyone who needs a parody or novelty wordmark quickly and does not want to open a vector editor: type the text, pick a colour, export the file. It is the wrong tool for production brand work, because the README documents no font control, no vector editing, and no asset management, and the TODO still lists custom fonts as unfinished. Before adopting it, confirm that Node.js 18+ and npm 10+ are available, that npm is the only package manager your team will run against the lockfile, and that the WTFPL 2 licence is acceptable for how you intend to redistribute the built site.

Frequently asked questions

Official sources

1. bestony/logoly on GitHub
2. Issues
3. License: WTFPL
4. Project website
5. README