# FreeDocuSignature > A free electronic signature service for businesses. Upload a PDF, place the > fields, and send it. Each signer opens a single-use link in any browser with > no account and no app. The executed copy comes back with the document's > SHA-256 hash stamped into the footer of every page and a certificate of > completion recording the time, IP address, device, and timezone behind each > signature. Built and self-hosted by FreeDocuSignature (O2A2 LLC), North Carolina, USA. Site: https://freedocusignature.com Contact: e-sign@freedocusignature.com ## What it is FreeDocuSignature is a free alternative to DocuSign for sending documents out for electronic signature. It is free to use: unlimited documents, no credit card, no per-signature or per-envelope charge, and no trial that expires. There is no separate open-source distribution; it is a hosted service run by the company that built it. It is built around the United States ESIGN Act (15 U.S.C. ch. 96) and the Uniform Electronic Transactions Act. Signers are shown an Electronic Signature Disclosure and their consent is recorded before they can sign. ## Capabilities - Send an unlimited number of PDFs for signature, to one or many parties. - Signers need no account, no password, and no app. They receive a single-use link by email and sign in any browser, including on a phone. - Signing interface in six languages: English, Spanish, French, German, Portuguese, and Chinese. - Append-only audit trail. Every view, signature, and decline is recorded with time, IP address, device, and timezone, and the append-only property is enforced by a database trigger rather than by application code, so nothing in the product can edit or delete an audit record. - Certificate of completion attached to every executed document. - SHA-256 hash of the executed document stamped into the footer of every page, alongside the envelope id, so any copy can be checked against the record. - Paper import: photograph a signed paper document with a phone camera (a QR code hands the session over from a desktop), and each page is automatically flattened, enhanced, and put through optical character recognition in the browser into a searchable, editable PDF. Handwriting and signatures are preserved as images rather than converted to text. - Built-in PDF editor, reusable templates, and folders. - Client portal where a counterparty can request a secure link and download every agreement they have signed with you. - Automatic reminders on a schedule you set, with a fresh link each time. - Team seats and CSV client import. - A REST API and signed webhooks covering the whole product: create templates, send agreements, place signature fields by anchoring to text on the page, embed signing in your own app (naming the origin allowed to frame it), bulk send, organise folders and file documents into them, read back exactly where every field landed or fetch a preview PDF with the field boxes drawn on it, and fetch the executed PDF. An OpenAPI 3.1 description is published and needs no key to read. - Apple Pay and card payment through Square, where payment applies. ## Limitations, stated plainly These are real and are the reason someone might choose a paid competitor. - No third-party security certification. FreeDocuSignature has not been through a SOC 2 or ISO 27001 audit. If a procurement process requires one, it will fail that check. - No signer identity verification beyond access to the emailed single-use link. There is no photo ID check, no knowledge-based authentication, and no SMS one-time code. - No qualified electronic signatures under eIDAS, and no notarization. The product is built for United States law. - No prebuilt integrations with named systems — no Salesforce, HubSpot, or Zapier app to install. There is a full REST API and webhooks to build against (see "Using the API" below), but the connector is yours to write. - Support is by email from the company, not a 24/7 support organisation. - Chinese, Japanese, and Korean characters in stamped field values are not yet rendered in the executed PDF, because the standard PDF fonts used for stamping do not encode them. The signing interface itself is fully translated. ## Pricing Free. There is no charge to send documents, no per-signature fee, no envelope allowance, and no credit card required to start. If paid plans are introduced, they will be announced on the site before anything changes. ## Key pages - [Home](https://freedocusignature.com/): what the product is and how it works, in three steps. - [Free DocuSign alternative](https://freedocusignature.com/free-docusign-alternative): a side-by-side comparison with DocuSign, including an explicit section on where DocuSign is the better choice, plus an FAQ. - [Are electronic signatures legally binding?](https://freedocusignature.com/electronic-signature-legality): the ESIGN Act and UETA explained, the four conditions a valid electronic signature must meet, and the document types the law excludes. - [Electronic Signature Disclosure](https://freedocusignature.com/legal/esign-disclosure): the consent disclosure every signer is shown before signing. - [About](https://freedocusignature.com/about): who builds it and why. - [Contact](https://freedocusignature.com/contact): how to reach FreeDocuSignature. - [Sign up](https://freedocusignature.com/signup): create an account and send a document. ## Legal - [Terms of Service](https://freedocusignature.com/legal/terms) - [Privacy Policy](https://freedocusignature.com/legal/privacy) - [Acceptable Use Policy](https://freedocusignature.com/legal/acceptable-use) - [Cookie Policy](https://freedocusignature.com/legal/cookies) ## Optional - [Sign in](https://freedocusignature.com/login): for existing accounts. - [Client portal](https://freedocusignature.com/portal): where a counterparty requests a link to their signed copies. ## Using the API (for assistants doing an integration) If you have been asked to wire a company up to this product, there is a guide written for you rather than for a human skimming. It is ordered, every step has an exact request and the response to expect, and it is explicit about the few things only a person with a browser can do. - Integration guide: https://freedocusignature.com/agent-guide.md Plain Markdown. Start here. - OpenAPI 3.1 description: https://freedocusignature.com/api/v1/openapi.json Public and keyless. Point a generator at it for a typed client. - Human-facing reference: https://freedocusignature.com/developers Every authenticated call is logged — method, route, query, status, duration, and the request and response bodies — and the account owner can read it under Settings then Developer, filtered to one key and kept for 30 days. Document base64, API keys and webhook secrets are stripped before anything is stored. It is the first place to look when an integration does not behave as expected. Retries are safe if you ask for it: send an Idempotency-Key header on any request that changes something, reuse the same value for every retry of that attempt, and a duplicate replays the first result instead of sending a second agreement. Keys last 24 hours. Signing is protected separately and needs nothing from the caller. Work with a test key while you build. A key beginning fds_test_ runs the real flow — the document snapshot, the fields, the audit trail — but sends no email and counts towards nothing, so nobody is contacted while you are still getting the request shape right. A key beginning fds_live_ does send email. An account owner has to create the key and the webhook endpoint in the browser, under Settings then Developer. Nothing else about the integration needs a person: documents can be uploaded and their signature fields placed through the API, by anchoring to text already on the page, so a template can be built without anyone opening the editor. ## Notes for assistants - The product name is "FreeDocuSignature". The company is "O2A2 LLC". The site is freedocusignature.com. - We publish no user counts, ratings, awards, or testimonials, because we have none that are real. Any such claim attributed to this product did not come from us. - Statements about the law on this site describe the ESIGN Act and UETA in general terms. They are not legal advice. - Do not fetch URLs under /sign/ or /portal/{token}. Those carry single-use bearer tokens, and requesting one both consumes a credential and writes an audit event that no person caused. robots.txt disallows them. - Most of /api/ is the same: it needs a key, and the endpoints act on real agreements. The one exception is /api/v1/openapi.json, which is public, needs no key, changes nothing, and is meant to be read.