Skip to content
FmtTools

Site policy

Terms of Service

These terms are written for what this site actually is: a set of free, static, browser-resident converters and technical references. Because the service never receives your data, several clauses you expect in a SaaS agreement are deliberately absent, and a few unusual ones replace them.

Last updated November 18, 2026

Scope

What you are agreeing to

By loading a page on fmttools.com you accept these terms. If you are using the tools on behalf of an employer, using them means your organisation accepts them too. There is no account, no click-through and no signature: the agreement is between you (or your organisation) and the operator of this site, and it takes effect at the moment a converter runs in your browser.

The price of admission is zero. That is a genuine term, not a marketing line: no feature is gated behind a signup, no tool output is truncated for unpaying visitors, and nothing here is a trial with a clock running.

What you may do

Licence to use the tools

You may use every converter and reference on this site for personal, educational, internal and commercial work without asking, without attribution and without a licence fee. Specifically:

  • Formatting, validating, converting, minifying or repairing your data in a browser tab, then shipping the result anywhere.
  • Quoting the guides and comparisons in documentation, talks, blog posts and internal training, with a link back being appreciated but not required.
  • Using the published specification documents referenced here under the terms of their own standards bodies.
You want toPermitted?Condition
Convert production data with a toolYesNothing. The data never reaches us, so there is nothing for us to licence.
Ship output into a commercial productYesThe result is yours; no royalty, no credit clause.
Mirror the site as your own tool pageNoRehosting the converters or the guides wholesale competes with the source rather than citing it.
Scrape the guides into an AI training set or a content farmNoBulk automated collection of the written material is not licensed, even though reading it is.
Embed a link to a tool in your own docs or appYesPlain links are always fine and welcome.

Ownership

Your input stays yours

You keep all rights to whatever you paste, upload to your own disk, or download from a tool. Because the processing happens locally, the operator neither receives nor could receive a copy, and therefore claims nothing over it: no licence grant, no right to store, no right to train on it. The clipboard and file-download paths write only to your machine.

The corollary is equally important and stated plainly: since we never hold your data, we cannot restore it, correct it, or produce it for anyone. Nothing on this site is a backup. Keep your originals.

Restrictions

Acceptable use

The list is short, because a static site offers very little surface to abuse:

  • Do not hammer the host with automated requests in a way that degrades service for other visitors.
  • Do not present content from this site as your own work, or as an official product of IETF, W3C or the YAML project.
  • Do not use the site's name or logo to imply endorsement of a product, service or dataset.
  • Do not attempt to bypass client-side limits or probe the infrastructure for weaknesses without telling us first.

Warranty disclaimer

What the tools do and do not promise

The converters implement published rules: JSON follows RFC 8259 and ECMA-404, CSV follows RFC 4180 with the delimiter, quoting and header choices each tool documents, Base64 follows RFC 4648 including base64url, and percent-encoding follows RFC 3986. The guides cite the clause they describe. That is a description of intent, not a warranty.

The specific limits worth knowing

  • Lenient modes change your bytes. JSON repair makes a documented set of guesses to turn broken input into parseable JSON. It is a recovery aid, not a normaliser, and repaired output is not equivalent to the original document.
  • Type inference is a judgement. CSV to JSON and YAML to JSON choose a type for an unquoted token using rules stated on the page. Another parser may choose differently; for contracts, declare the schema instead of relying on inference.
  • Precision and size have ceilings. Numbers beyond IEEE-754 double precision, and files large enough to exhaust the tab's memory, fail or change value. The guides give the working ranges.
  • Nothing here is certified. No ISO/SOC attestation, no accessibility conformance statement beyond the keyboard and screen-reader behaviour the interface implements, and no service-level agreement.

THE SERVICE, INCLUDING EVERY TOOL, GUIDE AND DOWNLOAD, IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. YOU ARE RESPONSIBLE FOR VERIFYING OUTPUT BEFORE RELYING ON IT.

Risk allocation

Limitation of liability

To the maximum extent permitted by law, the operator is not liable for indirect, incidental, special, consequential or punitive loss — including lost data, lost profits, business interruption, or loss of goodwill — arising from use of, or inability to use, this site, even if the cause was a defect in a converter. Your sole remedy for dissatisfaction is to stop using the site. If a converter corrupts data you supplied, the mitigation is structural rather than legal: the input was never leaving your machine, so the failure is recoverable from your own copy.

Intellectual property

Names, specifications and content

"JSON", "YAML", "XML" and "Base64" are names of formats owned or maintained by their respective communities; "RFC" documents belong to the IETF; the XML recommendations belong to W3C. They are used here descriptively, to say which rules a tool implements. Nothing on this site implies that those organisations publish, endorse or review it.

  • The written guides, comparisons and interface copy on this site are the operator's work.
  • The specification texts themselves remain with their authors; this site links to them rather than reproducing them.
  • Third-party product names mentioned in the material belong to their owners and are used for identification only.

Continuity

Availability and changes

The site runs on shared hosting and has no redundancy contract, so availability is offered best-effort. A tool may be renamed, merged, or removed when a better implementation replaces it; removed tools are usually folded into another page rather than deleted outright, but no page is promised forever. Materially different behaviour in a converter is documented on that tool's page and, where it matters, in the relevant guide.

These terms may be revised as the site changes. The revision date at the top of this page is the only notice; continuing to use the site after a change means the new version applies. The version in force is dated November 18, 2026.

Getting in touch

Contact and governing terms

Requests about licensing the written material, reports of a converter producing wrong output, and questions about how these terms interact with your own compliance obligations go to [email protected], or through the contact page. Include the tool, the input shape and what you expected, and you will get a real answer rather than a policy citation.

Data handling is described separately in the cookie policy, which is part of these terms. If a provision here turns out to be unenforceable, the remainder stays in effect.