<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[signplify]]></title><description><![CDATA[signplify]]></description><link>https://signplify.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6ae08b5afe7b8ead31913ca6/1ffc5bc6-d6e4-4a74-9d23-e4d5218e5a73.png</url><title>signplify</title><link>https://signplify.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 16:14:18 GMT</lastBuildDate><atom:link href="https://signplify.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[DocuSign vs Signplify: An Honest Comparison for Freelancers and Small Teams]]></title><description><![CDATA[Disclosure: I built Signplify, so I have an obvious bias. I will try to be fair, say where DocuSign is clearly better, and keep claims about both tools…]]></description><link>https://signplify.hashnode.dev/docusign-vs-signplify-an-honest-comparison-for-freelancers-and-small-teams</link><guid isPermaLink="true">https://signplify.hashnode.dev/docusign-vs-signplify-an-honest-comparison-for-freelancers-and-small-teams</guid><category><![CDATA[Freelancing]]></category><category><![CDATA[pdf]]></category><category><![CDATA[sign ]]></category><dc:creator><![CDATA[alimousa13]]></dc:creator><pubDate>Sat, 14 Nov 2026 16:32:36 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6ae08b5afe7b8ead31913ca6/0c945238-88c9-4b70-a971-c4e192e10f68.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><strong>Disclosure:</strong> I built Signplify, so I have an obvious bias. I will try to be fair, say where DocuSign is clearly better, and keep claims about both tools checkable.</p>
<p>If you freelance, run a small business or build products on your own, you will eventually need a contract signed. The two usual routes are a full e-signature platform like DocuSign or a lightweight tool that signs a PDF in your browser. They solve different problems, and picking the wrong one costs either money or evidence.</p>
<h2>The short version</h2>
<ul>
<li><strong>Choose DocuSign</strong> when you need signing order, a detailed audit trail, reminders, integrations, identity checks or a tool your counterparty already trusts.</li>
<li><strong>Choose Signplify</strong> when you need to sign or send a simple document occasionally, do not want to create another account, and care about keeping the file on your device.</li>
<li><strong>Use both</strong> if you have a few high-stakes agreements a year and a lot of everyday signing.</li>
</ul>
<h2>How the two tools are built differently</h2>
<p><strong>DocuSign is a cloud workflow.</strong> You upload a document, define recipients and fields, and DocuSign manages routing, notifications, authentication and records. The unit of work is an envelope, a package of documents sent to recipients. That model is what enables audit trails, reminders and integrations with other systems.</p>
<p><strong>Signplify is a set of browser tools.</strong> Signing and most PDF tools run client-side in JavaScript, so the file never leaves your device. <a href="https://signplify.com/tools/request-signatures/">Request Signatures</a> sends a PDF to other people through private links, and the file is encrypted in your browser before it is shared.</p>
<p>That difference in architecture explains most of the comparison below.</p>
<h2>Feature comparison</h2>
<table>
<thead>
<tr>
<th></th>
<th>DocuSign</th>
<th>Signplify</th>
</tr>
</thead>
<tbody><tr>
<td>Sign your own PDF</td>
<td>Yes</td>
<td>Yes, in the browser</td>
</tr>
<tr>
<td>Account needed to send</td>
<td>Yes</td>
<td>No, for the core tools</td>
</tr>
<tr>
<td>Send to multiple signers</td>
<td>Yes, with routing and signing order</td>
<td>Yes, via private links</td>
</tr>
<tr>
<td>Audit trail and completion record</td>
<td>Yes, a core feature</td>
<td>No full audit-trail workflow</td>
</tr>
<tr>
<td>Reminders and expiry</td>
<td>Yes</td>
<td>No automatic reminders</td>
</tr>
<tr>
<td>Templates and team sharing</td>
<td>Yes, on paid plans</td>
<td>No shared team templates</td>
</tr>
<tr>
<td>Integrations and API</td>
<td>Yes, depending on plan</td>
<td>No</td>
</tr>
<tr>
<td>Bulk send and payment collection</td>
<td>Higher-tier plans</td>
<td>No</td>
</tr>
<tr>
<td>Identity verification options</td>
<td>Higher-tier plans</td>
<td>No</td>
</tr>
<tr>
<td>Document creation</td>
<td>Limited</td>
<td>Free generators for contracts, NDAs, invoices and more</td>
</tr>
<tr>
<td>Where files are processed</td>
<td>Cloud</td>
<td>Your browser for most tools</td>
</tr>
</tbody></table>
<h2>Pricing and limits</h2>
<p>DocuSign sells per-user plans, and the important detail is the envelope allowance rather than the headline price. According to published reviews, the entry plan allows only a handful of envelopes per month, while the team plans include an annual allowance per user, with extra envelopes billed separately. Free access is generally aimed at signing documents someone else sends you, not at sending your own. Prices and limits change often, so check <a href="http://docusign.com">docusign.com</a> for the current numbers.</p>
<p>Signplify’s core tools are free to use without an account. Optional paid features may be added later, and any pricing will be shown clearly before you pay.</p>
<h2>What about legal validity?</h2>
<p>In many countries, including the United States, the United Kingdom, Canada and Australia, electronic signatures are recognized for a wide range of documents. Validity depends on intent, consent and the type of document, and some documents, such as certain wills and property transfers, have special rules.</p>
<p>What differs between tools is the evidence they create. A platform that records who signed, when and from where gives you more to rely on if a signature is ever disputed. A simple signature image proves much less. For anything with real financial or legal weight, use a process that records signing activity, and ask a professional if you are unsure. This is general information, not legal advice.</p>
<h2>A developer’s check: does the file leave your device?</h2>
<p>Do not trust a privacy claim, including mine. Open your browser’s developer tools, go to the Network tab, and sign a test PDF. If no request carries the file, it stayed local. The same test works on any tool. The result will tell you, for example, whether a tool uploads your PDF before it adds a signature.</p>
<p>This is a useful habit for contracts, IDs and forms that contain personal details.</p>
<h2>When DocuSign is the better choice</h2>
<ul>
<li>Several people must sign in a specific order</li>
<li>You need a detailed completion record for compliance or disputes</li>
<li>You want automatic reminders and expiry dates</li>
<li>You need integrations or an API, for example from a CRM or your own app</li>
<li>Your client insists on it, which settles the question</li>
</ul>
<h2>When Signplify is enough</h2>
<ul>
<li>You sign a few documents a month for yourself, a landlord or a client</li>
<li>You need to <a href="https://signplify.com/tools/sign-pdf/">sign a PDF</a>, <a href="https://signplify.com/tools/fill-and-sign-pdf/">fill in a form</a> or <a href="https://signplify.com/tools/signature-generator/">create a signature image</a></li>
<li>You want to avoid another account and another subscription</li>
<li>You care about keeping the file on your own device</li>
</ul>
<p>If you want a longer look at alternatives, I wrote about <a href="https://signplify.com/blog/looking-for-a-free-docusign-alternative-what-signplify-can-help-you-do/">a free DocuSign alternative</a> and a <a href="https://signplify.com/blog/signplify-vs-pandadoc-which-should-you-use-for-contracts-and-signatures/">comparison with PandaDoc</a>.</p>
<h2>A simple decision checklist</h2>
<ol>
<li>Does the document have serious financial or legal consequences? If yes, use a platform that records signing activity.</li>
<li>Do several signers need a fixed order or automatic reminders? If yes, use DocuSign or a similar platform.</li>
<li>Is it a simple one-off signature and you want zero setup? A browser tool is enough.</li>
<li>Does your client or counterparty require a specific tool? Use that one.</li>
<li>Are you unsure? Ask the other party and, for important documents, a professional.</li>
</ol>
<h2>FAQs</h2>
<h3>Is Signplify a replacement for DocuSign?</h3>
<p>For simple, occasional signing, it can be. For compliance-heavy workflows, signing order, reminders and integrations, DocuSign is the stronger choice.</p>
<h3>Is DocuSign free?</h3>
<p>DocuSign generally lets you sign documents that others send you without paying, but sending your own documents requires a paid plan or trial. Check the current plans on docusign.com.</p>
<h3>Do my files leave my device with Signplify?</h3>
<p>Signing and most PDF tools run in your browser. For Request Signatures the file is encrypted in your browser before it is shared.</p>
<h3>Are electronic signatures legally binding?</h3>
<p>In many places, yes, for a wide range of documents. Exceptions and local rules apply, so check requirements for important documents.</p>
<h3>Can I use both tools?</h3>
<p>Yes. Some people use a full platform for formal agreements and a lightweight tool for everyday signing.</p>
<p><em>This comparison reflects publicly available information about DocuSign at the time of writing. Its plans, prices and features change, so check docusign.com for current details. Not legal advice. Last updated: [11/11 ].</em></p>
]]></content:encoded></item><item><title><![CDATA[How to sign a PDF in the browser without uploading it (pdf-lib and canvas)]]></title><description><![CDATA[Article for Hashnode. Suggested tags: javascript, webdev, pdf, privacy. Subtitle: A small, practical approach to client-side PDF signing, with the pitfalls…]]></description><link>https://signplify.hashnode.dev/how-to-sign-a-pdf-in-the-browser-without-uploading-it-pdf-lib-and-canvas</link><guid isPermaLink="true">https://signplify.hashnode.dev/how-to-sign-a-pdf-in-the-browser-without-uploading-it-pdf-lib-and-canvas</guid><dc:creator><![CDATA[alimousa13]]></dc:creator><pubDate>Tue, 27 Oct 2026 11:41:17 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6ae08b5afe7b8ead31913ca6/9d084e1d-2318-4558-b916-e22c1e4ff663.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p><em>Article for Hashnode. Suggested tags: javascript, webdev, pdf, privacy. Subtitle: A small, practical approach to client-side PDF signing, with the pitfalls that cost me time.</em></p>
<p>Most online PDF signers ask you to upload your file to their server. For a lease, a contract or a form with ID details, that is a trade-off many people would rather not make. The good news: you can do the whole job in the browser. The file never leaves the user's device, and the code is shorter than you might expect.</p>
<p>This post walks through a minimal version: capture a signature on a canvas, stamp it onto a PDF with <a href="https://pdf-lib.js.org/">pdf-lib</a>, and download the result. I used the same approach in a free tool I run called <a href="https://signplify.com/">Signplify</a>, and I will point out the mistakes I made along the way.</p>
<h2>What we are building</h2>
<ol>
<li>A canvas where the user draws a signature.</li>
<li>A function that places that signature on a chosen page of a PDF.</li>
<li>A download button for the signed file.</li>
</ol>
<p>Everything runs client-side. There is no backend in this tutorial.</p>
<h2>Step 1: capture the signature</h2>
<p>Use pointer events so that mouse, touch and pen all work. Set <code>touch-action: none</code> on the canvas in CSS, otherwise phones will scroll instead of draw.</p>
<pre><code class="language-js">const canvas = document.querySelector('#sig');
const ctx = canvas.getContext('2d');
let drawing = false;
ctx.lineWidth = 2.5;
ctx.lineCap = 'round';
ctx.strokeStyle = '#111';

function pos(e) {
  const r = canvas.getBoundingClientRect();
  return [
    (e.clientX - r.left) * (canvas.width / r.width),
    (e.clientY - r.top) * (canvas.height / r.height),
  ];
}

canvas.addEventListener('pointerdown', (e) =&gt; {
  drawing = true;
  ctx.beginPath();
  ctx.moveTo(...pos(e));
});
canvas.addEventListener('pointermove', (e) =&gt; {
  if (!drawing) return;
  ctx.lineTo(...pos(e));
  ctx.stroke();
});
addEventListener('pointerup', () =&gt; (drawing = false));
</code></pre>
<p>The scaling in <code>pos</code> matters. If the canvas is displayed at a different size from its internal resolution, drawing without it makes the line appear offset from your finger.</p>
<p>A canvas is transparent by default, which is exactly what you want. Export it as PNG and the signature will sit on the page without a white box around it.</p>
<pre><code class="language-js">const pngBytes = await (await fetch(canvas.toDataURL('image/png'))).arrayBuffer();
</code></pre>
<h2>Step 2: stamp the signature onto the PDF</h2>
<pre><code class="language-js">import { PDFDocument } from 'pdf-lib';

export async function stampSignature(pdfBytes, pngBytes, { pageIndex = 0, x, y, width = 160 }) {
  const pdf = await PDFDocument.load(pdfBytes);
  const img = await pdf.embedPng(pngBytes);
  const page = pdf.getPage(pageIndex);
  const height = (img.height / img.width) * width;
  page.drawImage(img, { x, y, width, height });
  return pdf.save();
}
</code></pre>
<p>That is the core of it. The part that trips people up is where <code>x</code> and <code>y</code> come from.</p>
<h2>Step 3: the coordinate gotcha</h2>
<p>PDF pages measure from the bottom-left corner. The browser measures from the top-left. If you let the user drag the signature over a preview of the page, you need to convert.</p>
<pre><code class="language-js">const { width: pageW, height: pageH } = page.getSize();
const k = pageW / previewWidthInPx;       // preview pixels to PDF units
const sigW = 160;
const sigH = (sigImgHeight / sigImgWidth) * sigW;

const x = screenX * k;
const y = pageH - screenY * k - sigH;    // flip the Y axis
</code></pre>
<p>Here <code>screenX</code> and <code>screenY</code> are the top-left corner of the signature box inside the preview. I got this wrong the first time and my signatures landed in the mirror position at the top of the page. A quick test is to sign a corner of the page and see where it ends up.</p>
<h2>Step 4: download the result</h2>
<pre><code class="language-js">const bytes = await stampSignature(pdfBytes, pngBytes, { pageIndex: 0, x, y });
const url = URL.createObjectURL(new Blob([bytes], { type: 'application/pdf' }));
const a = Object.assign(document.createElement('a'), { href: url, download: 'signed.pdf' });
a.click();
URL.revokeObjectURL(url);
</code></pre>
<p>For the preview, render pages with <a href="https://mozilla.github.io/pdf.js/">pdf.js</a> to a canvas and place a draggable element over it. Keep the rendered width in a variable so you can compute <code>k</code>.</p>
<h2>Pitfalls I ran into</h2>
<ul>
<li><strong>Rotated pages.</strong> Some scanned PDFs have a rotation set on the page. Check <code>page.getRotation()</code> and adjust your coordinates, or the signature will appear sideways.</li>
<li><strong>Encrypted PDFs.</strong> <code>PDFDocument.load</code> can throw. Catch the error and tell the user the file is protected, instead of failing silently.</li>
<li><strong>Memory.</strong> Very large files can freeze a mobile browser. Show a size warning and avoid holding several copies of the bytes.</li>
<li><strong>High-DPI screens.</strong> Draw at a higher internal resolution than the displayed size so signatures stay sharp when zoomed.</li>
<li><strong>Typed and uploaded signatures.</strong> Support both. A typed one is just text drawn onto a canvas in a script font, then exported with the same code.</li>
</ul>
<h2>Does the file really stay on the device?</h2>
<p>Do not take anyone's word for it, including mine. Open your browser's DevTools, switch to the Network tab, and run the signing flow. If there is no request that carries the PDF, the file stayed local. You can do the same check on any tool you use, including <a href="https://signplify.com/tools/sign-pdf/">Signplify's Sign PDF tool</a>.</p>
<h2>Electronic versus digital signatures</h2>
<p>This approach places an image of a signature on the page. That is a common form of electronic signature, and electronic signatures are generally accepted in many countries, but whether one is valid depends on the document and on local rules. It is not a cryptographic digital signature backed by a certificate, and it does not create an audit trail. For high-stakes or multi-party agreements, use a platform designed for that. This is general information, not legal advice.</p>
<h2>Wrapping up</h2>
<p>Client-side signing is a good fit when privacy matters and the workflow is simple: one signer, one document. The whole thing is about fifty lines of code plus a preview. If you would rather try it than build it, the free tools are at <a href="https://signplify.com/">signplify.com</a>, no signup needed.</p>
<p><em>Disclosure: I am the creator of Signplify.</em></p>
]]></content:encoded></item></channel></rss>