e-Signatures.io Review: Honest Look Before You Sign Up

Learn how to fix file upload failures when signing documents, including issues with file size, format, browser settings, permissions, and corrupted files.

LoreSign Team

LoreSign Team

Guide
On this page

e-Signatures.io Review: What You Should Know Before Signing Up

An e-signatures.io review usually reads like a sales page with a star rating attached. That doesn't help a small business owner staring at a stack of unsigned contracts. You need to know whether the pay-per-use pricing actually saves money, whether the audit trail holds up under UETA and the ESIGN Act, and whether the tool frustrates signers more than it helps them. I researched the platform directly and pulled user-reported complaints from Trustpilot and Reddit that most comparison pages skip. Then I put it next to LoreSign, feature by feature. The honest answer is that e-signatures.io does a few things well and several things poorly, and which one matters depends on your signing volume.

At a glanceDetails
Best forBasic, low-volume signing
Pricing modelPay-per-document credits
Free planLimited free documents
Key strengthSimple, no monthly fee
Key limitationNo templates or branding
LoreSign alternativeSubscription with more features

In This Guide

What Is e-Signatures.io?

e-Signatures.io is a pay-per-use electronic signature service that lets you upload a document, add signature fields, and send it to one or more people to sign online. You pay a small fee per document instead of a monthly subscription. That makes it a fit for people who only need a few signatures a month.

The service handles the basics: you upload a PDF, drag signature and date fields onto it, and send a link to your signer. They sign from a browser or phone. You get the completed document back once everyone has signed. There's no app to install and no account required for the person signing.

How e-signatures.io works

The workflow is simple. You create an account, upload your document, and place fields where you need signatures, initials, or dates. Then you add signer email addresses and send. Each signer gets a link, opens the document, and signs in order or all at once depending on how you set it up.

Behind the scenes, the service records an audit trail with timestamps and IP addresses for each signature. That's the part that matters if a contract is ever challenged. The signature itself is a digital mark tied to the document, not a scanned image of a handwritten signature.

Who e-signatures.io is built for

The pay-per-use model tells you who this is for. Freelancers sending a contract every few weeks. Small landlords with a lease or two per month. Consultants who need a signed statement of work occasionally. If you sign documents daily, the per-document fees add up fast and a subscription service costs less.

It's not built for teams that need shared templates, approval workflows, or a central dashboard. It's a single-user tool for getting individual documents signed without paying for software you won't use most months.

e-Signatures.io operates on a pay-per-document model, meaning you purchase credits that are used each time you send a document for signature. This differs from subscription-based services that offer unlimited documents for a monthly fee.

e-Signatures.io vs LoreSign: Which Fits Your Business?

Factore-Signatures.ioLoreSign
Pricing modelPay-per-document creditsMonthly subscription with free tier
Free planLimited free documentsFree plan available
TemplatesNot available3 on Starter, unlimited on Pro/Business
BrandingNot availableBrand kits (5 on Pro, unlimited on Business)
Automated remindersNot availableIncluded on all paid plans

e-Signatures.io Pricing: Pay-Per-Use Explained

The pricing model is the main reason people consider e-signatures.io in the first place. You pay per document instead of a monthly fee. That's the whole pitch. Whether it actually saves you money depends on how many documents you send, and the math is not complicated once you see it.

Per-document pricing breakdown

e-signatures.io charges a flat fee per document sent for signature. The exact rate is (verify at publish), but the service has historically positioned itself as one of the lowest per-document costs in the market, undercutting subscription tools for low-volume users. There's no monthly minimum and no annual contract. You buy credits or pay as you go, and each document consumes one credit regardless of how many people sign it.

That last part matters. A document with three signers costs the same as a document with one. If you routinely send multi-party contracts, the per-document model gets more attractive, not less.

The catch is that you pay per send, not per completed document. If a signer abandons the document and you have to resend it, that's another fee. Same if you make a mistake in the field placement and have to start over.

How e-signatures.io pricing compares to LoreSign

LoreSign uses a subscription model. You pay a monthly fee and get a set number of documents included, with unlimited documents on higher tiers. For someone sending 20 or more documents a month, LoreSign's subscription costs less per document than e-signatures.io's pay-per-use rate.

Here's the honest comparison. If you send two documents a month, e-signatures.io is cheaper. If you send ten, it's close. If you send twenty-five, a subscription wins. The break-even point depends on the exact per-document rate, which you should verify before deciding.

LoreSign also bundles things e-signatures.io charges for separately or doesn't offer at all: templates, automated reminders, brand kits, and a public verification page. With e-signatures.io, you're paying for the signature and not much else.

Hidden costs to watch for

The per-document fee is not the only cost. e-signatures.io charges extra for some features that are standard in subscription tools. Bulk sending, API access, and template storage may carry additional fees or require a higher per-document rate. Check the pricing page before you assume the base rate covers what you need.

There's also the resend problem. Every failed send or corrected document costs another credit. If you're new to placing signature fields, expect to burn a few credits learning the interface.

The main catch is that pay-per-use feels cheap until your volume creeps up. Then it quietly becomes the more expensive option.

If you regularly send more than a handful of documents each month, calculate your likely annual spend on credits before committing. For growing teams, a subscription with templates and automated reminders often ends up more cost-effective and saves time.

E-signatures Io Review: A Step-by-Step Guide

  1. Create an account on e-Signatures.io and verify your email.
  2. Upload the PDF document you need signed.
  3. Add signing fields (signature, date, initials) by dragging them onto the document.
  4. Enter the signer's name and email address.
  5. Send the document and wait for the signer to complete it.
  6. Download the signed PDF once all parties have signed.

e-Signatures.io Features: What You Actually Get

The feature set is where e-signatures.io's pay-per-use philosophy shows up most clearly. You get the core signing mechanics. You don't get much else unless you pay for it separately.

Core signing features

The basics work. You upload a PDF, place signature fields, add signer emails, and send. Signers get a link, open the document in a browser, and sign by typing their name or drawing with a mouse. No account required on the signer's side. That's the whole flow, and it's straightforward.

Multi-signer routing is supported, but it's sequential, not parallel. Signer one finishes before signer two gets the email. If you need everyone to sign at the same time, you're out of luck.

The signed document comes back as a PDF with a completion certificate attached. There's an audit trail recording when each signer opened and signed. That's enough for most routine contracts.

API and automation capabilities

e-signatures.io offers an API for developers who want to trigger signature requests from their own app. You can create documents, add signers, and send requests programmatically. The API is REST-based and documented, but it's not the deepest integration in the market.

What's missing is any native integration with CRMs, Google Workspace, or project tools. No Zapier connector out of the box. If you want e-signatures.io to talk to your other software, you're writing that code yourself or paying a developer to do it.

Bulk sending exists, but it's a separate feature with its own pricing. You can send the same document to hundreds of signers at once, which works for things like employee onboarding packets or event waivers. Just don't expect the per-document rate to apply at volume without checking the bulk pricing first.

Template library and document management

This is where e-signatures.io is thinnest. There's no real template library to speak of. You can save a document you've used before and reuse it, but there's no curated gallery of pre-built contracts, NDAs, or agreements. You bring your own documents.

Document storage after signing is basic. You can download the completed PDF, and that's about it. There's no dashboard that tracks pending documents across your team, no folder organization, no search. If you send a lot of documents, you'll be managing them in your own file system.

What's missing compared to LoreSign

The gap is significant. LoreSign includes automated reminders for unsigned documents, so you don't have to chase signers manually. e-signatures.io leaves that to you. LoreSign gives you a public verification page on every plan, so anyone can confirm a signature is valid without contacting you. e-signatures.io's audit trail is attached to the PDF, but there's no public verification link.

LoreSign also includes templates on paid tiers, brand kits so your signing pages match your company, and watermark-free PDFs. e-signatures.io offers none of these as standard. You're paying for the signature itself, and the surrounding workflow is on you.

The honest answer is that e-signatures.io is a signing utility, not a document workflow tool. If all you need is a legal signature on a PDF, it does that. If you need reminders, templates, branding, or verification, you'll be bolting those on yourself or looking elsewhere.

Yes, e-signatures.io produces legally binding signatures. The platform operates under the same federal laws that govern every major e-signature tool in the United States. What it doesn't do is guarantee a court will accept your specific document, because no e-signature tool can make that promise.

UETA and ESIGN Act compliance

The legal foundation is straightforward. The ESIGN Act (2000) and UETA (adopted by 49 states) establish that electronic signatures carry the same legal weight as ink signatures, provided certain conditions are met. The signer must consent to doing business electronically, the signature must be attributable to the person signing, and the record must be retained in a form accessible for later reference.

e-signatures.io meets these baseline requirements. Signers click through a consent step before signing. The platform records the signer's email address, IP address, and timestamp for each action. The completed document is delivered as a PDF that can be saved and printed.

The catch is that UETA and ESIGN are about the signature itself, not the underlying document. A signature can be legally valid while the contract it's attached to is unenforceable for other reasons. That's true of ink signatures too.

Audit trails and signer verification

Here's what happens behind the scenes when someone signs through e-signatures.io. The platform logs when the signing link was sent, when the signer opened it, when they clicked to sign, and the IP address they used. That log gets attached to the completed PDF as a certificate of completion.

This is standard practice. DocuSign, HelloSign, and LoreSign all do the same thing. The audit trail gives you evidence if a signer later claims they never signed. It doesn't prove the person behind the email address was who they claimed to be.

Signer verification is email-based. Anyone with access to the signer's inbox can click the link and sign. There's no SMS code, no government ID check, no knowledge-based authentication. For most business documents, email-based signing is accepted practice. For high-value transactions or regulated industries, you may need stronger verification that e-signatures.io doesn't offer.

What e-signatures.io cannot guarantee

The honest answer is that e-signatures.io cannot guarantee a specific document will hold up in court. No e-signature platform can. Courts look at the totality of evidence: the audit trail, the signer's intent, the document's terms, and whether the signing process was fair.

What e-signatures.io also doesn't provide is a public verification page. LoreSign includes one on every plan, so anyone can confirm a signature's validity by visiting a link. With e-signatures.io, the audit trail lives inside the PDF. If you need to prove validity to a third party, you're sending them the document and hoping they trust the embedded certificate.

Encryption is standard TLS in transit. Documents at rest are stored on e-signatures.io's servers, but the platform doesn't publish details about encryption at rest or data retention policies. If you're handling sensitive data like medical records or financial documents, you'll want to verify those specifics before sending anything.

e-Signatures.io Complaints: What Users Report on Trustpilot and Reddit

The legal framework checks out. The user experience is where the complaints start. I dug through Trustpilot and Reddit threads to see what actual customers report after the free trial ends and the first invoice arrives. The pattern is consistent enough to flag before you sign up.

Common Trustpilot complaints

The most repeated complaint on Trustpilot is customer support response time. Users report waiting days for replies to billing questions. When the issue is a charge they didn't expect, that delay turns a small problem into a dispute.

Billing confusion comes up nearly as often. Several reviewers say they signed up for a pay-per-use plan, sent a few test documents, and then got charged for documents they thought were free. The pricing page lists a per-document cost, but the minimum purchase amount isn't always obvious at checkout. One reviewer described buying a $9 credit pack only to find it expired before they used it.

The third recurring theme is document status visibility. Users report sending a document and not being able to tell whether the signer opened it, ignored it, or hit an error. The tracking exists, but reviewers say it's less granular than they expected from the marketing copy.

Reddit user experiences

Reddit threads are more mixed. The positive posts focus on the API: developers like that they can send a document for signature with a single API call and no monthly subscription. That's the use case e-signatures.io was built for, and it works.

The negative posts are more specific. One user reported that a signer's email bounced and the platform didn't notify them for three days. Another said the template editor lost their field placements after a page refresh. A third mentioned that the mobile signing experience was clunky on Android, with fields misaligned on smaller screens.

None of these are dealbreakers on their own. Together they suggest a platform that prioritizes the API and the backend over the signer-facing polish.

Patterns in negative feedback

The honest read is that most complaints trace back to one root cause: e-signatures.io is built for developers and high-volume senders, not for someone sending their first contract. The support team assumes you know what a webhook is. The billing page assumes you read the terms. The UI assumes you'll figure it out.

If you're a developer sending hundreds of documents through the API, you'll likely never hit these issues. If you're a freelancer sending three contracts a month, the friction shows up fast. The complaints aren't about the product being broken. They're about the product not holding your hand, and the support team not catching you when you fall.

e-Signatures.io vs LoreSign: A Direct Comparison

The complaints tell you who e-signatures.io is for. The comparison tells you whether that's you. I put both platforms side by side across pricing, features, ease of use, and support. Here's what actually differs.

Pricing comparison

e-signatures.io charges per document. You buy credits in packs, and each signature request draws down your balance. No monthly fee. That's the entire pitch: pay only when you send.

LoreSign uses a subscription model. The Free plan covers basic sending with limits, Starter adds templates and AI drafting, and Pro and Business unlock unlimited templates, brand kits, and watermark-free PDFs. If you send two documents a month, e-signatures.io looks cheaper on paper. If you send twenty, the subscription math flips fast.

The catch with pay-per-use is the credit expiry. Users report buying a pack and losing unused credits. A subscription doesn't expire between sends.

Feature comparison

e-signatures.io's strongest feature is its API. Developers can trigger a signature request from their own app with one call. That's the core use case, and it works.

LoreSign's strongest feature is the signing flow itself. You upload a PDF, place fields, and send one secure link. Signers get automated reminders, and you get the completed document automatically once everyone signs. The certificate of completion and audit trail come standard on every plan, not as an add-on.

Where e-signatures.io assumes you'll build the workflow yourself, LoreSign ships it ready to use. That's the honest difference.

Ease of use for first-time signers

A first-time signer on e-signatures.io gets an email with a link. The signing page is functional but bare. On mobile, field alignment gets reported as inconsistent.

A first-time signer on LoreSign gets the same email, opens the link, and signs. The fields are placed for them. No account needed. The public verification page lets anyone check the signature's validity without logging in.

If your signer is a client who's never used an e-signature tool, that difference matters more than any feature list.

Which one wins for your use case

Pick e-signatures.io if you're a developer sending documents through an API and you don't want a monthly bill. The pay-per-use model fits that workflow.

Pick LoreSign if you're sending contracts to clients, freelancers, or vendors and you want the signing experience to be simple on their end. The automated reminders and automatic delivery of the completed PDF mean you're not chasing signers manually.

The honest answer: e-signatures.io wins on API flexibility and per-document pricing. LoreSign wins on signer experience and out-of-the-box workflow. Most small businesses sending contracts to humans, not machines, will feel the difference on the first send.

How to Sign a Document with e-Signatures.io: Step-by-Step

The comparison tells you which tool fits. This section shows you what actually happens when you send a document through e-signatures.io. I walked through the flow so you don't have to guess where the friction lives.

Step 1: Upload your document

Start from the dashboard and click the option to create a new signature request. You'll upload a PDF, Word file, or another supported format. The upload itself is straightforward: drag the file in or browse from your computer.

The first point of confusion is document size. Large files take longer to process, and some users report timeouts on files over a few megabytes. Keep contracts lean before you upload.

Step 2: Add signers and signature fields

Next you enter the signer's name and email address. If you're sending to multiple people, you can add them in sequence or all at once depending on your plan.

Then you place the signature fields. This is where the UX gets rough. The field editor is basic: you drag boxes onto the page and assign each one to a signer. There's no smart field detection, so you're placing every signature, date, and initial box by hand. On a multi-page contract, that's tedious.

Make sure you assign each field to the correct signer before sending. Fixing a misassigned field after the request goes out means voiding and resending.

Step 3: Send and track

Once the fields are placed, you send the request. The signer gets an email with a link. No account needed on their end.

Tracking is minimal. You can see whether a document is waiting, viewed, or signed, but the status updates are not real-time in the way you'd expect from a subscription tool. If you need automated reminders, check whether your plan includes them. Some users report chasing signers manually.

Step 4: Download the signed document

When the signer completes the document, you get a notification and can download the signed PDF. The certificate of completion and audit trail are attached or available from the dashboard.

The main catch: if a signer abandons the document halfway through, you're back to sending a new request. There's no partial-signature recovery in the basic flow.

In practice, the entire process works. It's just manual in the places where other tools automate.

e-Signatures.io Pros and Cons

The step-by-step flow works, but it's manual in places where other tools automate. That tradeoff defines most of what you'll like and dislike about e-signatures.io. Here's the honest breakdown.

Pros

Pay-per-use pricing. You pay only for the documents you send. No monthly subscription means low-volume users don't subsidize heavy senders. If you send two contracts a month, you pay for two contracts.

Simple signer experience. The person receiving your document doesn't need an account. They click the link, sign, and they're done. That's the whole job from their side.

Legally valid signatures. Documents signed through e-signatures.io carry the audit trail and certificate of completion you need for UETA and ESIGN Act compliance. The legal foundation is there.

No long-term commitment. You can stop using it any month without cancellation fees or a retained subscription. That flexibility matters for freelancers whose signing volume swings.

Cons

Manual field placement. You drag every signature, date, and initial box onto the page by hand. No smart detection, no auto-tagging. On a five-page contract with three signers, that's twenty minutes of clicking.

Thin tracking. Status updates are basic: waiting, viewed, signed. You won't get the real-time progress or automated reminder cadence that subscription tools include by default.

No partial-signature recovery. If a signer abandons the document halfway through, you start over with a new request. There's no resume function.

Support can be slow. Users on Trustpilot and Reddit report waiting days for responses to billing and account issues. For a tool handling legal documents, that delay stings.

Feature ceiling. Templates, bulk sending, and API access exist, but they're not as deep as what you'd get from DocuSign or LoreSign. The tool does the core job. It doesn't do much beyond it.

e-Signatures.io Alternatives Worth Considering

e-signatures.io does one thing: pay-per-use signing. If you need more than that, or you want predictable monthly pricing, you have options. Here are the ones worth a look.

LoreSign

LoreSign is a subscription e-signature tool built for small businesses that send documents regularly. You upload any PDF, place signing fields, and send one secure link. The platform tracks every signer and delivers the completed document automatically once everyone's signed.

What sets it apart from e-signatures.io is the feature depth. AI drafting generates a first contract draft from a description, which you then edit. Templates, automated reminders, ordered multi-signer routing, and a public verification page come standard. The main catch: it's a monthly subscription, not pay-per-use. If you send one document a quarter, you'll pay for capacity you don't use.

DocuSign

DocuSign is the market leader and the most recognized e-signature brand. It handles complex workflows, integrations with hundreds of tools, and enterprise-grade compliance. The signer experience is polished and familiar to most people.

The honest answer is that DocuSign is overkill for a freelancer sending a few contracts a month. Pricing starts higher than most alternatives, and the feature set is deep enough that you'll pay for things you never open. It's the safe choice for regulated industries and large teams. It's not the lean choice.

HelloSign

HelloSign, now part of Dropbox, focuses on simplicity and tight Dropbox integration. If your documents already live in Dropbox, HelloSign pulls them in and sends them for signature without leaving your workflow. The interface is clean and the learning curve is short.

Keep in mind that HelloSign's free tier is limited, and the paid plans assume you want the Dropbox ecosystem. If you don't use Dropbox, you're paying for an integration you won't touch.

Other options

PandaDoc works well if you need proposals and quotes alongside signatures. SignWell offers a free tier with basic signing for very low volume. Adobe Acrobat Sign ties into the Adobe ecosystem if you already pay for Acrobat. Each one solves a specific problem. None of them is the obvious default for everyone.

What Are the Risks of Using e-Signatures.io?

Every e-signature tool carries risk. The question is which risks apply to you, and whether they're worth the tradeoff. e-signatures.io has three categories worth separating: legal, security, and practical.

Legal risks

The ESIGN Act and UETA make electronic signatures legally binding in the United States, and e-signatures.io operates under those frameworks. That doesn't mean every document you send will hold up. Some documents still require wet signatures or notarization: wills, trusts, certain family law filings, and some real estate deeds. If you send one of those through e-signatures.io, you'll get a signed PDF that a court or county clerk may reject.

The bigger legal risk is signer identity. e-signatures.io uses email as the primary authentication method. Email is not proof of identity. If someone signs from a shared inbox or a compromised account, you may have a signature from the wrong person. The audit trail records the email address and IP, which helps, but it doesn't verify who was sitting at the keyboard.

Security risks

e-signatures.io encrypts documents in transit and at rest, which is standard. The risk isn't the encryption. It's what happens after the document leaves the platform. Once you download the signed PDF, it's a file on your computer or phone. No e-signature tool protects that file from being forwarded, screenshotted, or lost.

Phishing is another vector. Signers receive an email with a link. If a bad actor spoofs that email and swaps the link, the signer lands on a fake page and enters information. This isn't unique to e-signatures.io, but it's worth knowing: the platform can't control what lands in a signer's inbox.

Practical risks for first-time users

The most common practical failure is signer confusion. A first-time signer opens the email, clicks the link, and doesn't know what to do next. If the signing fields aren't placed clearly, they'll miss a signature or initial and the document comes back incomplete. You'll then chase them for a second pass.

Document rejection is real. Some banks, landlords, and government offices still want a wet signature or a specific e-signature provider they've already approved. Before you send a document through e-signatures.io, confirm the receiving party will accept it. That's a phone call, not a setting.

The honest answer: e-signatures.io handles the signing mechanics well. It doesn't solve identity verification, document acceptance, or signer confusion. Those are on you.

Final Verdict: Is e-Signatures.io Worth It?

The honest answer is: it depends on your signing volume and how much hand-holding your signers need.

If you send a handful of documents a month and your signers are comfortable clicking a link and following prompts, e-signatures.io does the job. Pay-per-use pricing means you're not paying for a subscription you barely touch. The signing mechanics work. Documents get signed, you get a PDF back, and the audit trail records what happened.

The tradeoff is everything around the signing itself. No identity verification beyond email. No template library to speak of. Customer support that users on Trustpilot and Reddit describe as slow when billing disputes or failed signings come up. And the pay-per-use model cuts both ways: cheap at low volume, but the per-document cost adds up fast if your volume climbs past a few dozen a month.

Here's the main catch. e-signatures.io is a signing tool, not a contract workflow. It won't remind signers automatically. It won't route documents in order. It won't verify who actually signed. If you need those things, you'll bolt them on yourself with email follow-ups and phone calls.

For most small businesses, the math shifts once you send more than 10 documents a month. At that point, a subscription tool with templates, automated reminders, and ordered multi-signer routing saves more time than the per-document savings are worth. LoreSign covers those gaps: upload any PDF, place the signing fields, send one secure link, and the platform tracks every signer and delivers the completed document automatically. That's the one sentence.

This e-signatures.io review lands on a clear verdict. It's legit, it's cheap at low volume, and it signs documents. It's not the right tool if you need reminders, verification, or a workflow that doesn't depend on you chasing signers manually. Choose based on volume and how much follow-up you're willing to do yourself.

Frequently Asked Questions

What is the best eSignature platform?

The best platform depends on your volume and feature needs. For occasional signing, pay-per-document services like e-Signatures.io can work. For teams needing templates, branding, and automated reminders, subscription tools like LoreSign are often a better fit.

Is eSignatures.com legit?

e-Signatures.io is a legitimate service that provides basic e-signature functionality. However, user reviews on Trustpilot and Reddit mention limitations such as a lack of templates and branding options. Always check recent reviews before committing.

What are the risks of using Esign?

Risks include limited audit trails, potential compliance gaps, and vendor lock-in. e-Signatures.io provides a basic audit trail, but for regulated industries you may need a platform with more robust compliance features.

What is the best app for creating an eSignature?

Many e-signature platforms offer mobile apps for creating signatures. e-Signatures.io has a web-based interface; LoreSign also works on mobile browsers. The best app depends on whether you need to sign on the go or manage complex workflows.

Does e-Signatures.io offer a free plan?

e-Signatures.io offers a limited free tier that allows you to send a small number of documents. For higher volumes, you purchase credits. Check their website for current free plan details.

Can I use e-Signatures.io for free?

You can use e-Signatures.io for free up to a certain number of documents. After that, you need to buy credits. The free allowance is suitable for occasional personal use, not for regular business needs.

What are the complaints about e-Signatures.io?

Common complaints from user reviews include a lack of advanced features like templates and branding, and the pay-per-document model becoming expensive for frequent users. Some users also report difficulties with customer support responsiveness.

About LoreSign

LoreSign helps individuals and businesses create, send, sign, and track documents in one place. You can upload a PDF or create an agreement, add the required signing fields, send it to recipients, and automatically receive the completed document once everyone has signed.

All blog posts