About Reeff

Reeff is a small independent project. It exists because most “free online converters” ask you to upload a private document to a server you know nothing about, watch a progress bar, and then solve a CAPTCHA to get your own file back. We thought the browser could do the work instead.

Who runs this site

Reeff is operated by Ripple Effect Technologies, registered in Malaysia, and built by the same small team that publishes Reeff.PDF. The code for both sites — this brand site and the toolkit at pdf.reeff.app — lives in public repositories in the rentaolab organisation on GitHub (https://github.com/rentaolab), including the commit history.

There is no content agency and no outsourced editorial queue behind these pages. The person who answers mail at reeff.app@proton.me is the same person who writes and tests the tools, which is also why replies sometimes take a day.

Why the local tools are free

A file processed in your browser costs us nothing per file: your device does the work, so there is no server bill to recover. That is why tools that run locally are free and unlimited, and why we do not put a quota counter or a “you have 2 conversions left” wall in front of them.

Features that genuinely need a server — cloud OCR, invoice verification, batch queues, syncing history across devices — are planned as pay-as-you-go. We would rather say that up front than hide a paywall behind a free trial.

How the guides are written and tested

• Each guide is written after using the tool on real files, then re-read against the current interface. They are not generated from a keyword list.
• Numbers are measured on the hardware and browser named in the guide. When something cannot be measured reliably, the guide says so and explains how to test it yourself instead of quoting a figure.
• Screenshots come from the live site. When an interface changes, the screenshot is replaced in the same commit as the change.
• Corrections are visible: the page keeps a publication date and an update date, and we change them when the text changes.

How often things change

Tools ship when they are usable, not on a calendar. The changelog records what changed and when it went live; the roadmap lists what we are working on and what we have decided not to build. Both are pages, not promises buried in an email.

What we will not do

• No fake countdown timers, no “only 3 spots left”, no invented testimonials or review scores.
• No claiming a file “never leaves your device” for a feature that does upload it. Anything that talks to a server is labelled before you click.
• No selling, renting or trading the addresses people give us for the waitlist.
• No thin pages published just to hold a keyword — if a page has nothing to say yet, it does not go live.

Getting in touch

Mail reeff.app@proton.me or use the contact page. Bug reports with the browser, the page count and the file size get a faster answer, because those three details usually explain the problem on their own.