Small tools, built properly, for the work nobody enjoys

Why this site exists

It started as a folder of scripts. We were doing client work — building sites, designing things — and losing an irritating amount of time to the same handful of jobs. Writing an invoice meant hunting for last month’s file, copying it, changing the numbers, and hoping the total was right. Getting a client’s photographs down to a size their site could actually serve meant opening image software, exporting at three settings, and comparing. Neither task was difficult. Both were slow, repetitive, and easy to get slightly wrong.

When we went looking for online tools to do them, the pattern was depressingly consistent: sign up to continue, three files a day on the free tier, a watermark across the output, or — most uncomfortably — upload your client’s unsigned contract to a server owned by someone whose retention policy you have not read.

So we built our own, and then it seemed obviously worth putting them somewhere public.

The one technical decision that shapes everything

Every tool on this site runs entirely inside your browser. Not “we delete your files after an hour” — there is no upload at all. Your image is decoded onto a canvas element on your own machine, re-encoded there, and handed back to you. Your invoice PDF is assembled in the tab you are looking at.

You do not have to take our word for this. Open your browser’s network inspector while you compress an image and watch for a request that never comes, or disconnect from the internet after the page has loaded and notice that everything still works.

That decision costs us things. We cannot offer accounts, saved history across devices, or server-side batch processing, and very large files depend on your device rather than our hardware. We think it is worth it: the most sensitive material anyone brings to a site like this — client contact details, unpublished photographs, a Wi-Fi password — never enters our custody, which is a much stronger promise than a well-worded retention policy.

Why we write the guides

A tool answers “how”. It does not answer “what should go on this invoice in the first place”, or “is an electronic signature going to hold up”, or “why did my PNG get bigger when I compressed it”.

Those questions have real answers, and most of what is written about them online is either thin, undated, or confidently wrong about which country’s rules apply. So we write the version we wanted to find: long enough to actually settle the question, explicit about jurisdiction, and linked to the primary source — the tax authority’s own page, the statute, the specification — so you can check us.

Our editorial policy sets out how we source, review and correct that work, including what we do and do not do with AI writing tools.

How the site is funded

Display advertising, and nothing else. There is no paid tier, no affiliate link, no sponsored post and no data being sold — the tools never send us your data in the first place, so there is nothing to sell even if we wanted to. Advertisers have no say in what we publish, and we do not know which ads land on which page.

We tell you this because “free” usually has a catch, and you are entitled to know what ours is: you see adverts, and we keep them out of the way of the content.

What we will not do

• Put a tool behind a sign-up form.
• Watermark output, or cripple it until you pay.
• Upload your files to a server in order to process them.
• Publish thin articles on subjects we do not work in, to catch search traffic.
• Take money to write about something favourably.

Who we are

Talentra's editorial team researches, drafts and fact-checks every guide on this site, and revisits each one when the underlying rules change.

The guides on this site are written by the same people who build the tools. When we explain what belongs on a US invoice, it is because we have written the invoice generator that produces one. When we write about image formats, it is because we have measured the output of our own compressor across hundreds of test files.

Every guide names the sources it relies on and links to the primary document — the IRS page, the GOV.UK guidance, the W3C specification — rather than asking you to take our word for it. Where a rule differs by country or is genuinely unsettled, we say so instead of flattening it into a single confident answer.

Get in touch

Corrections are the most useful thing you can send us, especially with a source attached. Feature requests and bug reports are welcome too. Write to info@talentrasolutions.com or use the contact page.