A Convertio alternative that uploads nothing, and where it stops
· 11 min read
Convertio uploads files to its cloud and caps free users at 10 conversions a day. ToolSura is a free Convertio alternative that converts in your browser.

Convertio is one of the most-used file converters on the web, and two things send people looking elsewhere: every file is uploaded to its servers, and the free plan is metered. Both are written down on its own pages.
This is the comparison, plus three things the vendor pages leave out: what a browser converter does to your file, where client-side conversion stops working, and how many formats ToolSura cannot do. Figures were read from Convertio's about page, formats page and help centre on 18 October 2026.
What Convertio is, and where the 309 formats sit
Convertio launched in 2014 and describes itself as a cloud service. Its homepage states the trade: "All conversions take place in the cloud and will not consume any capacity from your computer." That is true, and it is why the service handles video transcoding on modest hardware.
The scale figures come from the about page: more than 10 million monthly users and over a million files a day. Counting rows on the formats page gives 309 formats, not the advertised "300+" spread across 25,600 pairs. The breakdown is where the breadth claim thins: 108 images, 62 audio, 37 video, 23 documents, 23 archives, 20 vectors, 16 fonts, 10 presentations, 9 ebooks, and CAD, which is one format. DXF.
The free tier, and what paying for more buys
Ten credits is not ten files
Convertio's help centre states the free tier plainly: 1 GB maximum file size, 10 conversion credits per 24 hours, 10 concurrent conversions, and "There are no other restrictions."
The word "credits" matters more than the number does. A second help centre article explains the cost model: "Most lightweight conversions (e.g., documents, images, fonts, and audio) cost 1 credit per file. Resource-intensive conversions: Some complex conversions (e.g., videos or large multi-page documents) may require more credits." The real free ceiling is fewer than ten files for anyone touching video or a large document. Failures are refunded, since you are "charged only for conversions that complete successfully", and the old 100 MB cap is gone, replaced by 1 GB. A pricing page archived in March 2021 prices by file size and concurrency instead, with no credit system at all, which is where the stale figure comes from.
What the money buys
| Plan | Monthly | Annual billing | Credits a month | Max file size | Concurrent |
|---|---|---|---|---|---|
| Free | $0 | none | 10 per 24 h | 1 GB | 10 |
| Lite | $11.99 | $6.99 | 1,000 | 1 GB | 50 |
| Basic | $22.99 | $13.99 | 3,000 | 3 GB | 100 |
| Pro | $44.99 | $25.99 | 10,000 | 10 GB | Unlimited |
| Custom | from $54.00 | $32.42 | up to 1,000,000 | 20 GB | Unlimited |
Checked 18 October 2026 against the pricing page. The file-size column is the one most comparisons drop: paying buys headroom per file, not only credits. Convertio also advertises "Save up to 40% with annual plans", and every paid tier including Lite serves ad-free pages.
Privacy: what Convertio discloses
Convertio's privacy policy is more reassuring than its reputation suggests. It says plainly, "We do not read, look into or copy your files." Input and temporary files are deleted instantly after conversion, outputs when you close them or after 24 hours. The security page adds ISO 27001 certification, a separate sandbox per conversion, and German infrastructure under GDPR.
Two details sit against that. The company journals your IP address, file types, duration and success flag for a long time. And under the heading "Cookies, Analytics and Ads" it names Google Analytics and Google AdSense, then stops. Plenty of articles claim a consent banner disclosing 193 advertising partners. There is no such banner. That number appears nowhere on the site as a partner count, and no consent-management vendor loads at all. The absence is the observation.
Convertio also contradicts itself on scale, on live pages: the privacy policy says 300 TB converted a month, the about and security pages say over 1 PB. A first-party number is worth what checking it costs.
For a contract or a client file, a deletion promise still means the file sat on hardware you do not control. Moving the processing onto your own device ends the question, which is the argument behind privacy-first tooling more generally.
What the forums show
The conversations worth reading are requests, not bug reports, and the answer is the same each time.
In r/software, someone asking for an open source program like convertio.co so you can convert offline was handed Converseen, PhotoDemon and Hybrid. In r/privacy, someone wanting HTML to EPUB asked for a FOSS replacement for both CloudConvert and Convertio and was told "Calibre with Pandoc, is perfect." A third thread, an offline file converter, collected HandBrake, XMedia Recode and Shutter Encoder. A fourth, on picking a free video converter, turned on losslessness rather than convenience: "Sounds like it's re-encoding, which is not what you want."
The pattern is not that cloud converters break. It is that every answer was "run it locally", because every cloud converter shares two properties: your file crosses the network, and it joins a queue you cannot see.
How a conversion runs in the browser
ToolSura is a set of single-purpose converters, one page each, with no installer, no extension and no upload step.
Open the tool that matches the job, drop the file on the page, and download the result. Your browser reads the file from disk and does the work there, so there is no transfer to intercept, no queue to wait in, and no copy sitting in a data centre. With no account and no server-side storage, nothing is left behind to expire.
What browser conversion actually does to your file
Format lists and prices are the wrong things to compare, because every converter makes four decisions about your pixels that you never see. Tom Whitfield, who handles ToolSura's image format decisions, works through them in order.
Transparency flattens into a background colour
An image with an alpha channel cannot be represented in a format that has none, so converting to one replaces transparency with a background colour. A logo flattened onto black shows as a black rectangle around the mark on a light page, and as nothing on a dark one.
The background is not the converter's invention. The PNG specification says in section 11.3.5.1 that the bKGD chunk "specifies a default background colour to present the image against", and that "If there is any other preferred background, either user-specified or part of a larger page (as in a browser), the bKGD chunk should be ignored." The same flattened file can therefore present differently in two places, which is why the result looks broken on the site you did not test it on. Section 12.4 makes the point from the encoder's side. Where you want no background at all, the tRNS chunk is cheaper.
This is the one conversion to check before you point it at a batch.
Re-encoding stacks artefacts
Turning a JPG into a WebP is a second lossy encode of data that has already been through one. Lossy codecs introduce artefacts into the source material with each encode or reencode, so every pass adds a little. The PNG specification is blunter: colour space transformation at write time is a bad idea, and "it is better to store the data losslessly and incur at most one conversion when the image is finally displayed."
If the job is "make this smaller" and the source is already a JPEG, the artefact cost will often exceed the saving. Convert from the original whenever you still have it.
A dropped colour profile shifts every colour
An embedded ICC profile states what the samples mean, and the specification sets a precedence order when two declarations disagree: "An sRGB chunk or iCCP chunk, when present and recognized, overrides the gAMA chunk."
A converter that writes the samples out without carrying the profile forward, and without converting them into the space it is labelling them, produces a file that is internally consistent and now describes its colours under a different, usually sRGB-assumed, definition. The shift is far more visible than the compression artefacts people braced for. Either carry the profile forward or convert the samples. Doing neither is the most common way a correct conversion looks wrong.
Preview one file, then commit to the folder
Batch conversion is where mistakes get expensive, because the evidence arrives at the end. Whitfield's habit is the plainest one available: run a single file, open the output, compare its dimensions and its byte size against the input, then point the converter at the directory. Each of those four decisions is visible when you run the conversion and invisible when you upload it, which is the wider argument in what online converters do with your data.
Where client-side conversion breaks down
Client-side conversion holds the input, the decoded bitmap and the encoded output in memory at once, and the ceiling on all three belongs to the browser rather than to the site. MDN is careful about the figure because it depends on the machine: the maximum length "depends on the platform, browser and browser version", with an ArrayBuffer capped at 2 GiB minus 1 on 32-bit systems and 8 GiB on 64-bit from Firefox 89.
What binds in practice is decoded pixel count, not file size. A bitmap costs roughly four bytes per pixel before compression, and the conversion works on the decoded form. A 4,000 by 3,000 photograph decodes to about 48 MB of pixels whatever it weighs on disk.
So "no upload, no limit" ends where your own RAM ends. That is a real ceiling, and a different kind of one from a server quota: you can raise it by closing tabs, not by paying.
The alternatives you will actually be recommended, and where each one breaks
CloudConvert vs Convertio, and the three different meters
The general question of when to install something rather than open a tab has its own answer, set out in browser tools against desktop software. This is narrower: the programs that come back when you search for a Convertio replacement, checked 18 October 2026.
| Tool | Family | Licence | The one thing a browser converter cannot do |
|---|---|---|---|
| ImageMagick | Images | ImageMagick Licence, free for commercial use, not OSI-open | Batch pipelines and scripting that run unattended |
| FFmpeg | Audio, video | LGPL 2.1+, GPL where optional parts are enabled | All 62 audio and 37 video formats, unmetered |
| HandBrake | Video | GPLv2; Windows, macOS, Linux | Delivery presets for modern codecs |
| XnConvert | Images | Freeware for private or educational use only, €15.00 down to €6.50 commercial | Over 80 batch actions and watch-folder automation |
| IrfanView | Images | Freeware for non-commercial use only | Very fast batch processing, Windows only |
| Calibre | Ebooks | GPL-3.0 | DRM handling and format normalisation across nine formats |
| 7-Zip | Archives | LGPL and BSD-3, with an unRAR restriction | Reads more container formats than Convertio's 23 |
Three findings the comparison pages do not make.
Three cloud converters, three incompatible meters. Convertio meters conversion credits. CloudConvert gives 10 credits a day, 1 GB and five concurrent tasks. FreeConvert meters time instead, at 20 conversion minutes a day with a five-minute cap per file, and needs no account to get them. Credits and minutes cannot be added together, so a table lining the three up is comparing units, not allowances.
Switching websites does not fix the limit. CloudConvert's free tier has the same shape as Convertio's, ten credits a day and a 1 GB maximum file size, and it uploads your files too. It does publish per-category counts, 212 formats across 11 categories, which Convertio does not, but none of that makes it a privacy answer. Moving between converter sites changes which company holds your file; leaving the cloud changes the architecture. If the daily cap is why you came here, only the second one fixes it.
Two of them are not free in the sense most readers assume. XnConvert's own page calls it "FREEWARE (NO Adware, NO Spyware) for private or educational use (including non-profit organizations)". IrfanView says "Freeware for non-commercial use", and it ships for Windows only. Both need a licence line in the budget the moment somebody else is paying.
What ToolSura cannot convert
Here is the gap as a number, because a hedge is worse than a figure. ToolSura has no audio, video, archive, ebook, font, presentation or CAD converter at all: 158 of Convertio's 309 formats across seven families, plus most of the document, vector and camera RAW formats.
| Family | Convertio formats | Best free local answer | Licence | Platforms |
|---|---|---|---|---|
| Audio | 62 | FFmpeg | LGPL 2.1+, GPL with optional parts | Win, Mac, Linux |
| Video | 37 | FFmpeg, or HandBrake for presets | LGPL/GPL, GPLv2 | Win, Mac, Linux |
| Archives | 23 | 7-Zip | LGPL and BSD-3, unRAR restriction | Windows |
| Fonts | 16 | fonttools, Google woff2 | MIT, Apache-2.0 | Any |
| Presentations | 10 | LibreOffice Impress, headless | MPL-2.0 | Win, Mac, Linux |
| Ebooks | 9 | Calibre | GPL-3.0 | Win, Mac, Linux |
| CAD | 1 (DXF) | LibreCAD for 2D | GPL-2.0 | Win, Mac, Linux |
The boundary is architectural rather than a shortfall. Those seven families need a codec engine or a full office suite, and a codec engine is a large native dependency that does not belong in a page meant to load in a second. ToolSura covers what the browser already ships a decoder for, which is the memory ceiling above seen from the other side.
Convertio against ToolSura
| Convertio | ToolSura | |
|---|---|---|
| Where the work happens | Company cloud servers | Your browser, on your device |
| Price | Free at 10 credits a day; Lite is $11.99 a month, or $6.99 billed annually | Free, unmetered, no paid tier |
| Account | Pushed once you outgrow the free tier | Never |
| Works offline | No | After the page has loaded |
| Formats | 309, including audio, video, fonts, ebooks, CAD | Images, text and encodings, PDF, JSON, YAML, CSV, Markdown to HTML |
Privacy, price and limits point one way and breadth points the other, and the 158-format table is what that gap weighs. For video, audio, archives, ebooks and long-tail formats, use FFmpeg, HandBrake, 7-Zip or Calibre. For the routine work most people do in a week, an upload buys nothing except exposure.
Related Tools & further reading
- WebP to PNG/JPG converter: WebP screenshots and downloads into universally supported files, without an upload.
- PDF compressor: shrink a document to fit an email or form limit.
- Base64 encoder/decoder: encode text or files to Base64 and back.
- CSV to JSON converter: reshape spreadsheet exports for apps and APIs.
The image tools family adds resizing, SVG conversion and metadata inspection, and the PNG and JPG compressor covers the size work behind the format section above. How to compress images for the web goes further on the same ground, HTML to PDF handles the document side, and this page sits in the Tool Alternatives Hub.

Written by
Tom Whitfield
I start by splitting the formats into two groups, because most of the confusion comes from treating them alike. Lossless formats keep every pixel. Converting between lossless formats is safe in principle, though there is a catch: an image with an alpha channel cannot be represented in a format without one, and transparency silently becomes a background colour. That is the one conversion to check before you run it on a batch.
Lossy formats discard information on purpose. Converting a JPG to WebP re-encodes an already-encoded image, and the result carries the artefacts of both encodings. There is no reason to do that unless you need the format, and if you have the original you should convert from it every time. Colour profile is the other half.
An image with an embedded profile displayed on a system without one will have its colours shifted, and the shift is far more visible than the compression artefact people expected to see. Converting without handling the profile is the most common way an otherwise fine conversion looks wrong. I cover the format decisions by use: a photograph for display, a logo with transparency, an image with text in it where artefacts are unacceptable, and an image destined for print where colour space changes everything.
Batch conversion is where mistakes get expensive. I write about previewing a single file and reading the output size before running the directory. One more caution about alpha. Converting a transparent image to a format without transparency produces a background colour chosen for you, usually black, and on a dark page that reads as a black rectangle around the subject rather than as an error.