About floi
floi is a library of small tools that each do one job. Convert an image, format some JSON, pull a frame out of a video, count the words in a draft, make a QR code. These are the everyday jobs you currently solve by searching, landing on an ad-covered page, and handing your file to a stranger.
Look at what that habit costs and the shape of the problem appears. A PDF subscription for one job, an image service for another, a converter site with adverts for a third. Each one is a login, a renewal date and a file you posted to somebody else's server. floi is the argument that a browser can do all of it, in one place, without any of that.
There are 54 tools here today and 7 more named and in build. They sit on 6 shelves: media & images, text & writing, developer, documents & office, education & study, design & colour. The whole directory is on the home page.
How it is built
floi is a fully static site. Every page is pre-rendered HTML, served from Cloudflare's edge network, with no server-side code running on a page request. There is no file storage, and no tool uploads the file it works on to a server. File transfer sends it directly to your other device.
All the actual work happens in your browser. Your video is decoded by the browser's own media engine, frames are drawn to a <canvas>, images are re-encoded by the same codecs that display them, and even ZIP archives are assembled in the tab. The background remover runs its model on your own machine. The processing does not upload your files. Signed-in text work and settings save privately to your account.
Three parts of this site use a server, and each is worth naming. The file transfer tool sends a file from one of your devices straight to another, and two browsers cannot open a direct connection without first swapping their network addresses and encryption keys. A ten minute room does that swap and nothing else: it copies two short messages between the pair, never sees a filename or a byte of a file, and is destroyed as soon as they are talking.
The /geo lookup returns the country code Cloudflare attached to the request. It helps fill in the sign-up form. It stores nothing.
The third is an optional account. Signed in, your settings, typed or pasted drafts and numeric activity save automatically. Nothing about you is public. Files and text opened from files stay on this device. Every tool works fully while signed out, with text and settings kept on your device.
The ideas board lets you suggest tools and features. Anyone can read approved ideas. An account is needed to submit, vote, comment or report. New requests wait for review before appearing publicly.
Why the browser
Privacy is the obvious reason, but it is not the only one. A local tool is faster, because a large file never waits in an upload queue. It works on files that are too big or too sensitive to send anywhere. And it keeps working when the connection does not, since most tools here run offline once the page has loaded.
It is also why everything is free. Static files on a CDN cost almost nothing to serve, so there is no bill to cover with an account wall, a watermark or a daily cap.
What it costs, and what it will cost
Nothing, today, on every tool here. No account, no trial, no watermark, no counter and no card. That is not a launch offer waiting to expire.
It is worth being straight about the direction, though. floi will keep growing, and at some point there may be a paid option beside the free one. If that happens it will be built out of capabilities that do not exist here yet: pushing a few hundred files through one saved recipe in a single pass, chaining several tools into one step, keeping that setup across your devices. Work that is genuinely new, in other words.
What it will not be is a fence around something that is free right now. The paid file services mostly do not sell you a feature; they sell you the removal of a limit they added. iLovePDF stops a free account after two compressions and one OCR. TinyWow charges $20 a month, and what that buys is the absence of its own adverts and CAPTCHAs. Both prices were read off their pricing pages on 5 September 2026.
Every tool that is free on this site stays free, uncapped and unwatermarked. It is an easy promise to keep, because the reason it is free is architectural rather than generous: your processor does the work, so there is no per-file cost for anyone to pass on.
What gets built
The test for a new tool is whether a browser can do the job honestly and well. If it can, it belongs here rather than behind an upload form. If it cannot, the page says so instead of pretending.
Every tool has a guide beside it, and the guides are written the same way. Each one carries at least one thing measured here, on real files, with the method and the date next to it. Which image formats a browser can actually write, for instance, is a matrix that was tested rather than assumed.
What it does not do
floi does not download YouTube videos, and it cannot pull an arbitrary timestamp from a YouTube URL by itself. That is not a policy choice, it is a technical boundary: YouTube's player runs in a cross-origin iframe a page may not read, and its media servers do not permit cross-origin requests. Any site claiming otherwise is running a server that downloads the video for you.
The honest paths to an arbitrary frame are the ones floi offers. Capture what is on screen, or work from a file you already have in the frame extractor. Source resolution needs the source file. Download the video where you have the right to, then work from that.
Live screen capture is desktop only, because the browser API behind it does not exist on a phone. That is on the tool's own page too, rather than waiting to fail when you get there.
Copyright
A frame or a thumbnail is a derivative work of the video it comes from. Use your own footage, licensed material, or content that falls under fair use or fair dealing where you live. floi is not affiliated with, endorsed by, or connected to YouTube or Google.
Open by design
Because everything is client-side, you can verify all of it. Open your browser's developer tools and watch the Network tab. No request uploads your file. Google Analytics can send usage events, and signed-in text drafts and settings save privately. Turn Google Analytics off through Analytics settings in the footer. The privacy policy explains those requests and device pairing.