About
Small tools that finish the job and get out of the way
Tinapps is 83 focused browser tools across 11 categories. Every one of them opens with something already on screen, runs on your own machine, and needs no account.
Who publishes this
Tinapps is written and maintained by Hossein Shams, a software engineer. It is not a content farm and not a team — one person builds the tools, writes the guides, and answers the mail at hello@tinapps.com.
The site began as a pile of scripts kept for personal use: convert this image, check that contrast ratio, work out what a loan actually costs. Each one got a page when it turned out other people needed the same thing.
How the tools work
Almost every tool here runs entirely in your browser. When you drop a PDF on Merge PDF or an image on Image Compressor, the file is read by the page itself using the browser’s own APIs. It is never uploaded, never stored on a server, and never seen by anyone but you. Close the tab and the work is gone.
That is a design constraint rather than a marketing line, and it costs something: a browser cannot do everything a server can, and very large files are limited by your own machine’s memory. In exchange, the tools work offline once loaded, they are fast because nothing travels, and there is no queue, no watermark, and no file-size tier to buy.
Where a tool genuinely needs the network, the page says so on the page itself rather than in a policy. See the privacy policy for the full account of what does and does not leave your machine.
How the pages are written
Every tool page carries a guide underneath the tool: an ordered how-to, a worked example run end to end with real numbers, the judgement calls the tool cannot make for you, and the questions people actually ask. Those are written by hand, for that tool, by someone who built the tool.
Nothing here is generated at scale from a public dataset. A set of reference libraries — MIME types, network ports, file extensions, symbols — was built that way and is not published: compiled lookups are useful, but they are not written, and a site is fairly judged on the whole of what it puts out. They stay in the source, unpublished, until each one carries something its dataset does not already say.
When something here is wrong, it gets corrected. Corrections are welcome at hello@tinapps.com and are the fastest way to improve a page.
How it is paid for
The tools are free and there is no paid tier. Hosting is funded by advertising, and the site uses privacy-preserving analytics to understand which tools are worth more work. Neither of those changes the rule above: your files are still not uploaded, and what you type into a tool is not sent anywhere.
Ads are labelled and kept out of the working surface of a tool. A page will not be written because an advertiser wants it, and no tool result is influenced by one.
Getting in touch
Bug reports, tool requests, corrections, and business enquiries all go to the same place: the contact page.