sign.dropbox.com

Dropbox Sign (formerly HelloSign) turns a document into a signed agreement in four steps: choose a file, prep it for signature, send it, and let the signed copy save itself. The recipient does not need a Dropbox Sign account to review and sign. This workflow suits anyone sending sales contracts, NDAs, offer letters, or creative approvals, and it fits teams already working inside Dropbox, Google Drive, Salesforce, or OneDrive.

The four-step signing workflow

1. Choose your file

Start with a document from Dropbox or another connected app. You don't have to export or convert it first — the point of the integration is that the file you already have is the file you send.

2. Prep for signature

Add your signers, place the fields they need to fill in, and write a personalized message. This is where you decide who signs, where, and in what order, and where you set the context for the request.

3. Send the agreement

Recipients review and sign securely — no account required on their end. That removes the most common friction point in eSignature: asking a client or candidate to register before they can sign.

4. Save documents automatically

Signed documents save automatically to your preferred storage account. You don't have to download, rename, and re-file each completed agreement by hand.

What each step produces

Why the workflow is built this way

The design targets two bottlenecks: setup time and manual filing. Dropbox Sign describes getting started in minutes with an experience that's easy for a team to adopt, and it emphasizes fitting into existing workflows so there are fewer manual steps. The automatic-save step is the clearest example — it closes the loop without you touching the file again.

Security is handled at the platform level: agreements are protected with enterprise-grade security and audit trails, so each signature carries a record of who signed and when.

Where it connects

Dropbox Sign works with the platforms teams already use, including Dropbox, Google Drive, Salesforce, and OneDrive. If your documents already live in one of these, you can start a signature request without changing where your files are stored.

Choosing between the two options

Dropbox Sign offers two paths, and the right one depends on whether you're sending agreements yourself or building signing into a product:

• Send agreements with Dropbox Sign — share documents, collect electronic signatures, and automatically save completed copies. Starts at $15 / user / month (billed yearly).
• Integrate eSignatures with the Dropbox Sign API — build secure, branded signing directly into your website, app, or customer experience. Starts at $75 / 50 requests / month (billed yearly).

If your team sends contracts and NDAs manually, the first option matches that job. If you need signing to happen inside your own product, the API option is the one built for it.

Trying it before committing

Dropbox Sign offers a 30-day free trial, and you can cancel anytime during the trial. There's also a demo option if you want to see the workflow before starting. The platform holds a 4.7/5 G2 rating.

Common questions about the workflow

Does the recipient need an account? No — recipients review and sign securely without creating one.

Can I start from a file I already have in Dropbox? Yes. You can start with a document from Dropbox or another connected app.

Do I have to file signed copies myself? No. Signed documents save automatically to your preferred storage account.

What kinds of agreements does this cover? Sales contracts, NDAs, offer letters, creative approvals, and similar documents across departments.

Dropbox Sign fits teams that need to send, sign, and manage agreements without adding process overhead. Based on the product's own positioning, it supports sales contracts, NDAs, offer letters, and creative approvals, and it works across departments rather than for a single role. If your team already sends documents for signature through Dropbox, Google Drive, Salesforce, or OneDrive, it is designed to slot into that existing flow. If you need signatures embedded directly into your own website or app, that is a separate API product with its own pricing.

Who it is built for

The site frames Dropbox Sign around "every team" and "work across departments," which points to a few concrete profiles:

• Sales teams sending contracts and order forms for signature
• HR and recruiting sending offer letters and onboarding paperwork
• Legal and operations handling NDAs and routine approvals
• Creative and marketing teams running approval sign-offs
• Any team already inside the Dropbox ecosystem that wants signature requests to start from where the document already lives

The common thread is volume plus repetition: teams that send the same categories of documents often and want fewer manual steps between "request" and "signature."

What it actually does

The workflow described on the site has four steps:

1. Choose your file — start from Dropbox or another connected app.
2. Prep for signature — add signers, fields, and a personalized message.
3. Send the agreement — recipients review and sign securely, and no account is required on their end.
4. Save documents automatically — completed copies go to your preferred storage account.

Two details matter for evaluation. First, signers do not need a Dropbox account, which removes a common friction point when sending to clients or candidates. Second, signed documents are saved automatically to your chosen storage, so you are not manually filing completed agreements.

Where it fits into existing workflows

Dropbox Sign lists integrations with Dropbox, Google Drive, Salesforce, OneDrive, and more. The practical value is that you can initiate a signature request from a tool your team already uses instead of switching to a separate signing product.

This matters most if your documents already live in one of those platforms. If your team stores contracts in Salesforce and approvals in Google Drive, the integration story is the reason to consider Dropbox Sign over a standalone eSignature tool. If your documents live somewhere else entirely, that advantage is smaller.

Security and compliance signals

The site states that agreements are protected with "enterprise-grade security and audit trails." Audit trails are the relevant feature for teams that need a record of who signed what and when — a standard requirement for contracts, NDAs, and HR documents. The site also carries a 4.7/5 G2 rating, which is a third-party signal rather than a product claim.

Two products, two use cases

Dropbox Sign splits into two offerings, and the choice depends on whether you are signing documents yourself or building signing into software.

If you are an end user or a team sending contracts, the standard product is the fit. If you are a developer or product team that needs signing as a feature inside your own software, the API is the relevant option — and the pricing model changes from per-user to per-request.

How to decide

Choose Dropbox Sign if most of these apply:

• You send contracts, NDAs, offer letters, or approvals regularly
• Your documents already live in Dropbox, Google Drive, Salesforce, or OneDrive
• You want signers to sign without creating an account
• You want completed documents filed automatically
• You need audit trails for compliance or record-keeping

Look elsewhere or evaluate further if:

• You need signing embedded in your own product (check the API instead)
• Your documents live outside the listed integrations and you do not want to move them
• You only sign a handful of documents a year and per-user pricing does not make sense

The 30-day free trial with cancellation anytime during the trial is the lowest-risk way to test whether the workflow matches how your team actually sends documents.

Dropbox Sign connects with the platforms teams already use for storage, CRM, and productivity, so signature requests can be sent from those tools and completed documents can be saved back automatically. According to the site, the named integrations include Dropbox, Google Drive, Salesforce, and OneDrive, with the stated goal of fitting into existing workflows and reducing manual steps. If your team works primarily inside one of those platforms, you can likely keep your current process rather than adopting a separate signing tool.

Named integrations

The site lists these platforms as part of the "Works with the tools you already use" section:

The page describes this set as "including" those tools, which means the list shown is not presented as exhaustive. For a tool not named on the page, treat availability as unconfirmed rather than assumed.

What the integrations actually do

Two capabilities are described on the page, and they map to different stages of the signing process:

• Send from your existing tools. Signature requests can be started from Dropbox or other connected apps, which the site frames as fewer manual steps along the way.
• Save completed documents automatically. Signed documents can be saved to your preferred storage account without a manual download-and-upload step.

The workflow itself is described in four steps: choose your file, prep for signature (add signers, fields, and a personalized message), send the agreement, then save documents automatically. Recipients review and sign securely, and the page states no account is required for them.

How to decide whether the integrations cover your stack

Use these questions to check fit before committing:

1. Where do your source documents live? If they sit in Dropbox, Google Drive, or OneDrive, the send-from-storage path matches the described workflow.
2. Where do signed copies need to end up? The automatic-save feature is described as saving to your preferred storage account — confirm your target storage is among the supported options.
3. Does your process run through a CRM? Salesforce is the only CRM named on the page, so if your pipeline lives elsewhere, verify support before assuming it.
4. Do you need signing embedded in your own product? That is a separate path — the Dropbox Sign API — rather than a standard integration.

Pricing context for each path

The page gives two starting points, both billed yearly:

• Dropbox Sign (sending agreements): starts at $15 / user / month.
• Dropbox Sign API (embedded signing): starts at $75 / 50 requests / month.

A 30-day free trial is offered, with cancellation allowed anytime during the trial. The page does not state which integrations are available on which plan, so if a specific integration is essential, confirm it against the plan you intend to buy rather than assuming it is included at every tier.

Practical next step

If your documents and signed copies both live in Dropbox, Google Drive, or OneDrive, the described integrations should let you keep your current storage habits and add signing on top. If your workflow depends on a tool not named on the page, or on a specific plan tier, verify that combination directly before starting the trial.

Dropbox Sign offers two paid tracks: a standard eSignature plan starting at $15 per user per month (billed yearly) for sending agreements, and an API plan starting at $75 per 50 requests per month (billed yearly) for embedding signing into your own product. Both come with a 30-day free trial that you can cancel anytime during the trial period. If you only need to send and manage documents, the standard plan is the right fit; if you're a developer building signing into a website or app, the API plan is the one to evaluate.

The Two Pricing Tracks at a Glance

Dropbox Sign separates its pricing by how you intend to use it, not just by volume.

The standard plan is priced per user, so cost scales with the number of people on your team who send agreements. The API plan is priced per request volume, so cost scales with signing activity rather than seats.

What the Standard Plan Covers

The send-agreements plan is built around a simple workflow: choose a file, prep it for signature, send it, and let signed copies save automatically.

• Send from where you already work. Signature requests can go out from Dropbox or other everyday tools, reducing manual steps.
• Recipients don't need an account. People you send to review and sign securely without signing up.
• Automatic saving. Completed documents save to your preferred storage account.
• Cross-department use. The same plan supports sales contracts, NDAs, offer letters, and creative approvals.
• Security and audit trails. Agreements are protected with enterprise-grade security and audit trails.

This is the plan to pick if your goal is to replace printing, scanning, and emailing PDFs with a tracked signing process.

What the API Plan Covers

The API plan is for teams that want signing to happen inside their own product rather than in a separate tool. It lets you build secure, branded signing directly into a website, app, or customer experience. The entry price of $75 per 50 requests per month (billed yearly) makes it a fit for lower-volume integrations; higher volumes would move you up the pricing tiers listed on the API pricing page.

How the Free Trial Works

Both tracks offer a 30-day free trial, and you can cancel anytime during the trial. The trial is the practical way to test two things before committing:

1. Whether the standard workflow fits your team's habits (try sending a real contract or NDA through the full cycle).
2. Whether the API's request-based pricing matches your expected signing volume (estimate your monthly requests before the trial ends).

Because the plans bill yearly, the trial is also your window to confirm that annual billing suits your budget and usage pattern.

Which Plan Should You Choose?

Use this as a decision shortcut:

• You send agreements to clients, candidates, or partners → standard plan, $15/user/month billed yearly.
• You want signing embedded in your own website or app → API plan, $75/50 requests/month billed yearly.
• You're unsure about volume or adoption → start the 30-day free trial on the track that matches your use case, and cancel during the trial if it doesn't fit.

Dropbox Sign also carries a 4.7/5 G2 rating, which is worth checking alongside the pricing pages if you want third-party signal on reliability before you commit.

For current tier details above the starting prices, check the Dropbox Sign pricing page and the API pricing page, since both list the full plan breakdowns.

Dropbox Sign is an electronic signature service, formerly known as HelloSign, for sending, receiving, and managing legally binding eSignatures. It fits teams that need to collect signatures on sales contracts, NDAs, offer letters, or creative approvals without adding a separate, complex signing process. The site describes it as a way to "send, sign, and manage agreements without the extra complexity," and it offers a 30-day free trial with the option to cancel anytime during the trial.

What you can do with Dropbox Sign

The core job is moving an agreement from "sent" to "signed" while keeping a record of what happened. According to the site, the workflow has four steps:

1. Choose your file — start with a document from Dropbox or another connected app.
2. Prep for signature — add signers, fields, and a personalized message.
3. Send the agreement — recipients review and sign securely, with no account required on their end.
4. Save documents automatically — completed documents are saved to your preferred storage account.

Beyond the basic send-and-sign loop, the page highlights these capabilities:

• Fits into existing workflows — send signature requests from Dropbox or other everyday tools, with fewer manual steps.
• Fast setup — the site says teams can "get up and running fast with an intuitive experience."
• Cross-department use — support for sales contracts, NDAs, offer letters, creative approvals, and more.
• Security and audit trails — each agreement is protected with enterprise-grade security and audit trails.

Who it's for and where it fits

Dropbox Sign is positioned for "every team" rather than a single department. The use cases named on the page — sales contracts, NDAs, offer letters, creative approvals — suggest it suits anyone who regularly needs a countersigned document back. If your team already stores files in Dropbox, Google Drive, OneDrive, or works in Salesforce, the integrations are the main draw: the site says it connects with "the platforms your team relies on every day."

Two ways to use it

The page presents two distinct products, and the choice depends on whether you're signing documents yourself or building signing into something you own.

Both options start with a 30-day free trial, and the site notes you can cancel anytime during the trial. Pricing shown is the starting tier billed yearly; check the current pricing pages for the full plan breakdown before committing.

What to verify before you decide

• Volume and seats — the $15/user/month and $75/50-requests/month figures are starting points. Match them against how many senders and how many signature requests you actually expect.
• Integration coverage — confirm the specific tools your team uses (Dropbox, Google Drive, Salesforce, OneDrive, and others are named) appear in the current integration list.
• Recipient experience — the site states recipients can sign without an account, which matters if you send to external parties who shouldn't have to register.
• Trial terms — the 30-day trial and cancel-anytime language come from the page; verify the exact terms at signup.

If your main need is collecting legally binding signatures on routine business documents, Dropbox Sign's standard product covers it. If you need signing built into your own app or site, the API is the relevant option.