Are Electronic Signatures Legally Binding in the U.S.?

The short answer

An electronic signature is legally binding in the United States as long as the document is not one of the few that the law excludes, and as long as the person meant to sign. That's the core rule; ordinary contract law and, for some consumer documents, ESIGN's consent rules still apply. There are no "levels" of signature, no required certificates and no approved vendors. U.S. law is technology-neutral on purpose.

So the real questions are practical: is this kind of document allowed, did the other person agree to sign electronically, and could you show a judge how the signature got there? The rest of this guide answers each one.

The two laws: ESIGN and UETA

Two layers of law work together.

• The ESIGN Act (Electronic Signatures in Global and National Commerce Act, 2000, 15 U.S.C. § 7001 et seq.) is federal. It covers any transaction "in or affecting interstate or foreign commerce," which in practice is almost every business deal.
• UETA (Uniform Electronic Transactions Act, 1999) is a model law written by the Uniform Law Commission. Each state passes it as its own statute. It has been adopted by 49 states, the District of Columbia, Puerto Rico and the U.S. Virgin Islands. Washington adopted it in 2020 and Illinois in 2021.
• New York is the one state that never adopted UETA. It has its own Electronic Signatures and Records Act (ESRA), which gives an electronic signature "the same validity and effect" as one signed by hand. ESIGN applies there too.

The core rule is word for word almost the same in both laws:

"A signature, contract, or other record relating to such transaction may not be denied legal effect, validity, or enforceability solely because it is in electronic form."

15 U.S.C. § 7001(a)(1) (ESIGN Act) · Official source

UETA adds the other half: "If a law requires a signature, an electronic signature satisfies the law" (UETA § 7(d)). More detail in the ESIGN Act explained and what is UETA.

What counts as an electronic signature

The definition is deliberately broad:

"The term "electronic signature" means an electronic sound, symbol, or process, attached to or logically associated with a contract or other record and executed or adopted by a person with the intent to sign the record."

15 U.S.C. § 7006(5) (ESIGN Act) · Official source

That covers:

• A signature drawn with a finger or mouse on a phone or computer.
• A typed name in a signature field, or even at the end of an email, if the person meant it as a signature. See can you type your name as a signature?
• A checkbox or an "I agree" button, when it's clear what you're agreeing to.
• An image of your handwritten signature pasted into a PDF. It counts, but it's the hardest to prove. See is a scanned signature legally binding?

What doesn't automatically count: a signature block that your email program adds to every message. Courts have said that, on its own, it shows no intent to sign anything in particular.

The four things courts look at

Neither statute gives a checklist, but the same four questions come up whenever an electronic signature is challenged. They follow directly from the text of ESIGN and UETA.

1. Intent to sign. The person did something on purpose to sign this document: drew a signature, typed a name, tapped "Sign." The definition above requires it ("with the intent to sign the record").
2. Consent to do business electronically. UETA applies only between parties who have agreed to deal electronically, and that agreement "is determined from the context and surrounding circumstances, including the parties' conduct" (UETA § 5(b)). Opening a link and signing usually shows it. For consumers, when a law requires information to be given in writing, ESIGN asks for more: a specific disclosure and affirmative consent (§ 7001(c)).
3. Association with the record. The signature must be "attached to or logically associated with" the specific document. A signature floating in a separate email is weak; one embedded in the signed PDF and tied to its fingerprint is strong.
4. Record retention. If a law requires a contract to be in writing, the electronic version must be "capable of being retained and accurately reproduced for later reference" by every party entitled to keep it (§ 7001(e)). In practice: everyone gets a copy of the final signed PDF. MultiDocs deletes the document 30 days after signing, so each signer should download and keep theirs.

What can't be signed electronically

ESIGN § 7003 leaves out a short list. For these, the usual rules (paper, witnesses, formal service or a court system) still apply:

• Wills, codicils and testamentary trusts.
• Adoption, divorce and other family law matters.
• Court orders, notices and official court documents.
• Notices that cut off water, heat or power; notices of default, foreclosure or eviction on a primary residence; cancellation of health or life insurance; product recalls that affect health or safety.
• Documents that must travel with hazardous materials.
• Most of the Uniform Commercial Code, except sales and leases of goods (Articles 2 and 2A).

States can add their own exclusions (California has a long list), and documents that need a notary, such as most deeds and many powers of attorney, follow notary law. Full detail in which documents can't be signed electronically and e-signature vs. notarization.

How to prove who signed

This is where most disputes are won or lost. UETA says a signature is attributable to a person "if it was the act of the person," and that this "may be shown in any manner, including a showing of the efficacy of any security procedure" (UETA § 9). In plain English: if someone says "that's not my signature," you need evidence of the process.

Good evidence looks like this:

• The email address or phone number the signing link was sent to, so only that person could open it.
• The date and time of each step: sent, opened, signed.
• The IP address, device and browser used to sign.
• A cryptographic fingerprint (a SHA-256 hash) of the final document, which proves nothing changed after signing.

The Federal Rules of Evidence also let electronic records be authenticated with a certification describing the process that produced them (Rule 902(13) and (14)). Every document signed through MultiDocs ends with a certificate of completion recording those details, plus a unique signer code, which can support that kind of evidence. Anyone can check the file at multidocs.app/verify.

What courts have actually said

A few published cases show the pattern. They're worth knowing because they're cited again and again:

• Ruiz v. Moss Bros. Auto Group, Inc., 232 Cal. App. 4th 836 (2014): an employer couldn't enforce an arbitration agreement because it never explained how the employee's electronic signature got onto the document or why it had to be his.
• Espejo v. Southern California Permanente Medical Group, 246 Cal. App. 4th 1047 (2016): the employer won because it described the process: a unique username and password, and the date, time and IP address of the signature.
• Fabian v. Renovate America, Inc., 42 Cal. App. 5th 1062 (2019): the company lost again for failing to show how the signature was made and verified.
• Khoury v. Tomlinson, 518 S.W.3d 568 (Tex. App. 2017): a Texas court accepted the sender's name in an email header as a signature, because the email showed intent to agree.
• Cunningham v. Zurich American Insurance Co., 352 S.W.3d 519 (Tex. App. 2011): an automatic email signature block was not enough, because nothing showed intent to sign.

The lesson in every one: courts don't question electronic signatures as such. They question signatures nobody can explain.

This is general information, not legal advice. For your specific situation, ask a lawyer licensed in your state.