Brandtree

Who owns Dropbox Sign?

Dropbox Sign is owned by Dropbox (the United States, NASDAQ: DBX), which has owned the brand since 8 February 2019.[1][2]

Evidence: Dropbox, Inc. Annual Report on Form 10-K filed 2026-02-20, SEC EDGAR, 20 February 2026. Verified from filings; last checked .

Key facts

Current owner
Dropbox, Inc. verified
Owned since
Owner HQ
🇺🇸 United States, San Francisco
Origin
🇺🇸 United States
Category
Internet & digital › Digital services › Productivity & developer tools
Parent ticker
NASDAQ: DBX
Last verified
· 2 sources

About Dropbox Sign

Dropbox Sign is an eSignature and document workflow platform according to Dropbox's 10-K, which lists it among the company's products. It began as HelloSign: Dropbox completed its acquisition of JN Projects, Inc. (d/b/a HelloSign) on 8 February 2019 and later rebranded the product as Dropbox Sign.

Ownership timeline of Dropbox Sign

Owners of Dropbox Sign over 2019 to 2026 Dropbox 2019–present Dropbox 201920202021202220232024202520262027
  1. 2019 – present Dropbox [1][2] verified

Where Dropbox Sign sits in Dropbox

Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.

Where Dropbox Sign sits in Dropbox Tree of 7 brands under Dropbox. Dropbox Dropbox Sign DocSend Dropbox Dropbox Dash Dropbox Paper FormSwift and 1 more

Open the full Dropbox ownership tree →

See the full Dropbox brand portfolio (7) →

Other brands owned by Dropbox

Dropbox controls 7 brands on Brandtree, 7 of them in internet & digital.

Also in internet & digital

All Dropbox brands →

Other brands in productivity & developer tools, and who owns them

Dropbox has more brands in productivity & developer tools on Brandtree than any other owner: 7 of 33.

BrandOwnerOwner based in
Baidu Drive Baidu 🇨🇳 China
4PS Hilti 🇱🇮 Liechtenstein
Google Cloud Alphabet 🇺🇸 United States
Angi IAC 🇺🇸 United States
Base44 Wix 🇮🇱 Israel
DingTalk Alibaba 🇭🇰 Hong Kong
Amazon Web Services Amazon 🇺🇸 United States
OpenTable Booking Holdings 🇺🇸 United States

Every brand in productivity & developer tools and its owner →

About the owner: Dropbox

Dropbox is a publicly listed company headquartered in San Francisco, United States, founded in 2007. Brandtree records 7 brands under its control, and it is listed as NASDAQ: DBX.

Dropbox, Inc. is a San Francisco company that its 10-K for the year ended 31 December 2025 says was founded in 2007 and trades on Nasdaq as DBX. It sells a cloud storage and content collaboration platform plus related document products, including Dropbox Sign, DocSend, FormSwift, Dash and, since July 2024, Reclaim.ai.

Dropbox: full profile, brands and acquisition history →

🇺🇸 Dropbox Sign and other American brands

Brandtree records a controlling owner for 2,570 brands that began in the United States. 492 of them (19%) are now controlled by a company headquartered in another country; Dropbox Sign is not one of them.

All American brands and who owns them →

Frequently asked questions

Who is the parent company of Dropbox Sign?

The parent company of Dropbox Sign is Dropbox, a publicly listed company headquartered in the United States.

Is Dropbox Sign American?

Yes. Dropbox Sign originated in the United States and its owner, Dropbox, is also headquartered in the United States.

Since when has Dropbox owned Dropbox Sign?

Dropbox has owned Dropbox Sign since 8 February 2019.

Is Dropbox Sign still owned by Dropbox?

Yes. As of 29 October 2026, Dropbox Sign is still owned by Dropbox. The ownership record was last checked against primary sources on that date.

Sources (2) & corrections

Last verified . Every ownership fact above is backed by one of these primary documents. Numbers in brackets in the text refer to this list.

  1. [1] Dropbox, Inc. Annual Report on Form 10-K filed 2026-02-20 — SEC EDGAR, SEC Form 10-K, published 20 February 2026; retrieved 3 October 2026.
  2. [2] Dropbox, Inc. Form 10-K for the year ended December 31, 2019 — SEC EDGAR, SEC Form 10-K, published 21 February 2020; retrieved 28 October 2026.

Report a correction Opens a pre-filled GitHub issue. See our corrections policy.