About Us

Textavia came out of laziness, honestly. A few of us kept needing the same things: convert a HEIC to JPG, pretty-print some JSON, generate a quick UUID. We'd waste five minutes finding a converter online, deal with ads, wonder if our file was being stored somewhere. So we built our own set of tools for internal use. Then friends started asking for the link. Then strangers on Reddit. So we cleaned it up and made it public.

At this point there are 176+ tools on the site, split across text, code, image, and generator categories. The team is small and fully remote. We care about two things more than anything: the page should load fast, and your data should stay on your machine.

Everything here is built by us. No white-labeling, no third-party widget dressed up with a new skin. The case converter is our code. The JSON formatter is our code. The image encoder is our code. It all lives in one repo and gets shipped together.

Most of the tools run entirely in your browser. Text converters, hash generators, the random tools, code formatters. Your input never hits a server. For images, we lean on the Canvas API and Web Workers so your photos don't leave your machine.

There are a few exceptions. Some image formats (like HEIC on non-Apple browsers) need server-side processing because the browser simply can't decode them natively. Every tool page says which one it is: look for the in-browser or server-side label. Don't trust us? Open DevTools, go to the Network tab, run a conversion. If it's client-side you won't see a single upload request.

Where we do use open-source libraries (sharp for server-side image work, for example), we pin versions and audit them. No ads get injected into the pipeline. No tracking pixels. No analytics on your file content.

Privacy isn't a feature we market — it's the byproduct of how the tools are built. If the browser can do the job, we don't touch a server. That means no data collection, no session recording, no selling user behavior to ad networks. Period.

For the handful of tools that do require server-side conversion, uploaded files are processed and immediately discarded. We don't store, cache, or log the content. Full details are in our Privacy Policy.

The how-to sections, format comparisons, and FAQ answers you see on tool pages are written by our team. Yes, we use AI during the research phase to gather facts faster. But a human reads every draft, rewrites it, tests the tool against what the text claims, and only then publishes it. If a paragraph doesn't match what the tool actually does, we scrap it.

For anything that relies on a formal spec (say, how AVIF compression works or what RFC 4648 says about Base64 padding), we link straight to the source. MDN, the W3C spec, the IETF doc. We're not going to paraphrase Wikipedia and pretend it's original research.

You'll see published dates, updated dates, and author names on tool pages. Some security-adjacent tools also have a "Reviewed by" label. That label only shows up when someone actually reviewed the page. We're not going to slap a five-star rating on our own work.

For the full editorial process, see Editorial Policy.

Small team. Developers, a designer, a couple of writers. All remote. We've spent way too many hours debating whether JPEG quality 83 or 85 produces a better result for a specific test photo, and whether a JSON formatter should keep trailing commas or strip them. That's the vibe.

Individual profiles and published work are over on the Authors page.

Textavia is owned, operated, and published by Caravaca Labs, LLC, a US-based venture studio that builds and operates practical web applications and developer tools. Caravaca Labs is the parent company behind Textavia and several other digital products.

We started in early 2025 with maybe a dozen text converters. It's grown to 176+ tools since then. Most new additions come from one of two places: something we needed for a client project, or a suggestion that showed up in our inbox more than once.

We can be reached via the Contact page. We typically respond within two business days. For tool-specific bug reports, please include the tool URL and what you expected to happen.

Email: Email available after page load

Publisher: Caravaca Labs, LLC