Pillowthought

A five-minute task should take five minutes. You should finish with a smaller image, a signed PDF, or an answer to your question, and get back to whatever you were doing. That is the ambition behind Pillowthought.

Too much everyday software makes you negotiate for the result. Create an account. Verify your email. Upload the document. Discover that the download is behind another screen. Somewhere along the way, fixing a file became an administrative undertaking.

I wanted a place for the small jobs to stay small. Tools you can open, understand, use, and leave. A little less friction in a day already full of it.

§The result is the point

Say someone sends you a form. The outcome you want is a completed document you can send back. Or you have a photograph that is too large to attach: you want a smaller file that still looks good. Or a service returns a wall of JSON and you need to find the field that explains why your afternoon has gone sideways.

Pillowthought brings those jobs into one place. You can sign and merge PDFs, resize and compress images, convert files, compare text, and make unreadable data legible. The homepage lets you paste text or drop a file and find a useful next step. You can arrive with the thing that needs fixing before you know the name of the tool that fixes it.

That last part matters. Choosing software is work. Learning its vocabulary is work. Remembering which of twelve websites handled the previous file is work. A useful collection earns its place by reducing that overhead each time you return.

§Privacy starts before the upload

A document can contain a signature, an address, a salary, or a piece of somebody else's life. A photograph can carry the coordinates of their home. Even an innocuous-looking log can contain something you would rather keep to yourself. Having a small task does not mean having unimportant data.

Most Pillowthought tools process their input on your device, inside the browser. For those tools, your file stays with you while the work happens. You do not have to hand over a document merely to rearrange its pages, or send a picture away to change its dimensions.

This is a practical form of privacy: reducing how often your data changes hands. Every unnecessary transfer creates another place where you have to trust someone else's retention policy, security, and judgement. Keeping the computation beside the file removes that transfer from the task.

Some outcomes require a server. Sharing a note needs storage; checking whether a website is up needs a request from elsewhere. Optional AI actions also send input for processing when you invoke them. The tools distinguish local, edge, and AI processing so you can make that choice before handing anything over. Privacy depends on an intelligible boundary, and that boundary should be visible.

§Less ceremony, more finished work

The tools are usable without creating an account. You can come in through the homepage or bookmark the one you need. The controls follow the same visual language across the collection, so familiarity carries from one task to the next.

Low friction includes the exit. A tool should give you a result you can take away: a file, a piece of text, something ready for the next step. Finishing a conversion should let you finish the conversion. There is no virtue in prolonging a visit once the job is done.

That is the standard I want to hold this project to. How quickly can someone recognise what to do? How much of their information must they surrender? How much attention does the interface demand before they get something useful back? Every extra decision needs to justify itself against the size of the original task.

Pillowthought is a growing attempt to make everyday software suck less. Keep private work private wherever possible. Make the next action obvious. Let people finish and leave with their afternoon intact.

If something needs fixing, bring it to Pillowthought.