Is Formatho free to use?

Yes! All Formatho tools are completely free and run entirely in your browser. No signup required, no credit card needed.

Is my data safe with Formatho?

Absolutely. All Formatho tools run 100% client-side in your browser. Your data never leaves your device. Zero tracking, zero storage, zero uploads.

What tools does Formatho offer?

Formatho offers free developer tools including JSON/YAML converter, Base64 encoder, JWT debugger, SQL formatter, hash generators, QR code generator, regex tester, security headers analyzer, and blockchain tools.

Do I need to create an account to use Formatho?

No account needed. Simply visit any tool page and start using it immediately. All tools work instantly without any registration.

How does Formatho protect my privacy?

Formatho uses zero server-side processing. Every tool executes directly in your browser's JavaScript engine. No data is ever sent to our servers. We have zero tracking, zero analytics cookies, and zero third-party data sharing.

Does this tool work offline?

Once the page loads, the tool works completely offline since all processing happens client-side in your browser.

Do I need to install any software?

No installation required. Simply open the tool in any modern web browser and start using it immediately.

SAML Metadata Generator

Generate SP or IdP SAML 2.0 metadata XML — client-side, nothing uploaded

SP details

entityID (usually your metadata URL)

Assertion Consumer Service (ACS) URL

Single Logout (SLO) URL (optional)

NameID format

validUntil (days, 0 = omit)

Signing certificate (PEM, optional)

AuthnRequestsSigned WantAssertionsSigned

Metadata XML

<?xml version="1.0"?>
<EntityDescriptor
  xmlns="urn:oasis:names:tc:SAML:2.0:metadata"
  entityID="https://sp.example.com/saml/metadata">
<SPSSODescriptor AuthnRequestsSigned="false" WantAssertionsSigned="true" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
  <SingleLogoutService
    Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect"
    Location="https://sp.example.com/saml/sls"/>
  <NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:persistent</NameIDFormat>
  <AssertionConsumerService
    Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
    Location="https://sp.example.com/saml/acs"
    index="0" isDefault="true"/>
  </SPSSODescriptor>
</EntityDescriptor>

About the Saml Metadata Generator

SAML metadata is the XML contract between an SP and an IdP: entity IDs, endpoint URLs, NameID formats, and the signing certificates. Hand-writing it is error-prone — one wrong binding URI or a certificate pasted with headers breaks the trust exchange — and most online generators receive your real endpoints and certificates on a server.

This generator produces standards-compliant SAML 2.0 metadata for either side of the flow. Fill in the entity ID and endpoints, pick a NameID format, optionally paste your signing certificate (the PEM body is embedded into the KeyDescriptor), and download the XML. Element ordering follows the SAML metadata schema so strict parsers accept the result, and everything is assembled in your browser.

How to use

Choose SP or IdP depending on which side you operate.
Enter your entityID (usually your metadata URL) and the ACS/SSO and SLO endpoints.
Paste your signing certificate PEM so partners can validate your signatures.
Download or copy the generated metadata and register it with your IdP or SP.

Frequently Asked Questions

What is a SAML metadata file? ▾

An XML document describing a SAML entity to its partners: its entityID (unique name), endpoint URLs (where assertions are delivered for an SP, where login requests go for an IdP), supported NameID formats, and signing certificates in KeyDescriptor elements. SPs and IdPs exchange metadata to establish trust — often by uploading the file or pasting its URL into admin consoles like Okta, Entra ID, or Keycloak.

Is the generated metadata complete enough for production? ▾

It covers what a standard SP/IdP pairing needs: entityID, ACS/SSO and SLO endpoints, NameID format, signing certificate, and the WantAssertionsSigned/AuthnRequestsSigned flags, with schema-correct element ordering. Enterprise IdPs may also want organization details, contact persons, or encryption certificates — add those before production. The XML is a correct starting point, generated locally from your values.

Is this tool free to use? ▾

Yes! This tool is 100% free. No signup, no credit card, no limits. It's part of Formatho's privacy-first developer toolkit.

Is my data safe? Does this tool send data to a server? ▾

Absolutely. This tool runs entirely in your browser. Your data never leaves your device. Zero server-side processing, zero tracking.