The Case Against Making You Sign Up
A few months back I needed to turn one HEIC photo into a JPEG for a visa form. The first converter I found let me pick the file, ran a progress bar to the end, and then covered the download button with a modal asking me to create a free account. It wanted an email address, a password, a click on a confirmation link, and agreement to terms I was never going to read, with a pre-ticked newsletter checkbox riding along. The site spent about two seconds converting my photo. I spent four minutes on the ceremony around it, and the confirmation email went to spam first.
I run Toolium, a set of free browser utilities for small jobs: converting a file, resizing an image, formatting a blob of JSON. Toolium has no accounts. You cannot register even if you ask nicely. I want to lay out the reasoning, partly because people ask, and partly because I think the signup wall in front of a ten-second task deserves more suspicion than users give it.
Who the account is for
No visitor to a file converter has ever written in to request a login page. Operators add accounts because accounts do work for the operator, and I think users deserve a plain description of that work.
The first job is the email list. Once you verify an address, the operator owns a channel to you that outlives the visit; you came for one conversion, and the drip campaign now treats you as a lead. The second job is metrics. You can chart registered users in ways you cannot chart anonymous visits, and a curve of monthly active accounts reads better in an investor deck than a curve of page views, because it implies a relationship instead of traffic. The third job is lock-in. When your history and presets live behind a login, leaving costs you something, and small switching costs multiplied across thousands of users become what growth teams call retention. The fourth job sits on the balance sheet. A user table is an asset in an acquisition, and a company holding half a million verified emails sells for more than a company holding a well-ranked URL, even when both did the same conversions for the same people.
None of those jobs touches your file. The conversion runs the same whether or not the operator knows your name, which makes the account pure overhead on your side of the table and pure infrastructure on theirs.
What the wall costs you
The costs land quietly, which I suspect is why the pattern survives.
You gain another password. Perhaps your password manager absorbs it, perhaps you reuse one from somewhere else, and reused passwords on small utility sites are the raw material of credential-stuffing attacks. You gain another breach surface, because that converter now holds your email and a password hash on infrastructure maintained by people you know nothing about, and a two-person tool site does not staff security the way your bank does. Your inbox gains a new correspondent as well: an onboarding sequence in week one, a feature announcement in week two, a we-miss-you message in month three, each carrying an unsubscribe link that may or may not do anything. You also accepted terms you did not read, which for a throwaway tool is rational behavior, and the design relies on exactly that.
You paid all of this for a task that occupied ten seconds of your day. The relationship the signup created has no further content. The converter and you were never going to build anything together. You wanted a JPEG.
The engineering I get to skip
Everything above is the user's side of the argument. The operator's case for skipping accounts strikes me as at least as strong, and I rarely see anyone make it in public.
Toolium stores nothing on a server. The file tools run inside your browser, so your machine does the processing and the file never reaches me. I never ask you to log in, and I keep no record of what you did. That one decision removed whole categories of work from my life as the person who maintains the site.
- I have no user table, which means I will never sit through the 3 a.m. migration on it that everyone who runs one eventually describes.
- I maintain no authentication code. Session handling, password hashing, login rate limiting, lockout logic, OAuth callbacks: each of those is a place where one mistake becomes a security advisory, and I have written none of them.
- I built no password-reset flow, so I answer no password-reset email. Anyone who has run a small product knows what fraction of the support inbox that removes.
- A breach of my servers would yield no credentials and no personal records, because none exist there. I cannot leak what I never collected.
- When a data-deletion request arrives under GDPR or a law like it, my reply is short and true: I hold nothing about you. Teams with user tables budget real hours for that correspondence, and mine rounds to zero.
A quieter benefit sits underneath those. Auth code drags in dependencies, and dependencies age. Every library in a login path puts you on one more upgrade treadmill and adds one more supply-chain worry, and I carry none of that weight. My attack surface is a set of pages that process files in your browser, and I can hold most of it in my head.
I work on this site alone. Every hour I do not spend on auth becomes an hour on the tools, and the tools are the only reason anyone shows up. On a small utility site the account system can grow to rival the complexity of the product it wraps, and that ratio should embarrass more operators than it does.
Where an account earns its keep
I hold nothing against accounts as a category. An account makes sense once a product carries state that must outlive the session or pass between people.
Sync earns it: when you start work on a laptop and continue on a phone, some server has to know both devices belong to you, and identity is how it knows. Collaboration earns it, because two people editing one document need to know who is who and who changed what. Long-lived projects qualify too. A codebase you will touch for years, or the invoices behind a client relationship, carry state worth protecting behind a login, and billing has to attach a payment to a person regardless of anything else.
Now hold a file converter against that list. The state lives for the length of one conversion. You have nothing to sync, because the output leaves with you when you close the tab. You have no one to collaborate with, because converting a file is not a group activity. The project ends before the progress bar finishes animating. An account bolted onto that workload is a toll booth on a footpath.
The part where it costs you
Statelessness has a price, and you pay a share of it, so I would rather name it than hide it behind a privacy halo.
Toolium keeps no history. When you come back tomorrow, the site holds no memory of you, so you will find no recent files and no saved presets waiting. If you resize the same batch of product photos every morning, you drag the same folder in every morning. Your settings cannot follow you from the office laptop to the machine at home, because nothing follows you anywhere. A competitor with accounts can offer every one of those conveniences, and for a heavy daily user they carry real weight.
My judgment is that the trade favors most visitors most of the time. The median visit to a utility site involves one task, done once, in a hurry, and for that visitor memory has no value while the wall has a definite cost. Someone converting forty files a day with the same settings might do better with a paid desktop tool that keeps a preferences file, and I would rather admit that than pretend a browser tab with amnesia suits every workflow.
What you get instead
You judge a tool that asks for nothing on the ten seconds it occupies. Either it converts the file or it fails, and you learn which within the visit. I find that discipline useful for myself as well. With no retention chart to flatter me, the only number left is whether the people who arrive get the thing they came for, and the only lever that moves it is making the tools better.
The fair follow-up is how the site pays for itself without a user list. Display ads, which is a compromise of its own, and you may reasonably ask whether an ad-funded site gets to lecture anyone about email lists. I think the two differ in kind: an ad occupies a rectangle for the length of your visit, while a verified email address follows you home and knocks whenever the sender pleases. One of those you close with the tab.
If you are curious how the site runs, I keep a short about page. It loads without asking who you are, which as of this writing still counts as a distinguishing feature.