Brandtree

Who owns DocSend?

DocSend is owned by Dropbox (the United States, NASDAQ: DBX).[1]

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
Owner HQ
🇺🇸 United States, San Francisco
Origin
🇺🇸 United States
Category
Internet & digital › Digital services › Productivity & developer tools
Parent ticker
NASDAQ: DBX
Last verified
· 1 sources

About DocSend

DocSend is described in Dropbox's 10-K as a secure document sharing and analytics platform. DocSend Inc., a Delaware company, appears in the list of subsidiaries filed as Exhibit 21.1 to the same 10-K. The filing does not state the acquisition date, so none is recorded here.

What Dropbox's annual report says about DocSend

Sentences about DocSend from Dropbox's latest annual filing[1], copied word for word.

How often Dropbox names DocSend in its annual report

A plain count of the times the name appears in the text of each annual report, not counting the start of a sentence. A brand that an owner writes about more is usually one it treats as central. The brand is named less often than it was three years earlier.

Annual report filedTimes DocSend is named
202610
202514
202420

Ownership timeline of DocSend

  1. Current owner Dropbox [1] verified

Where DocSend sits in Dropbox

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

Where DocSend sits in Dropbox Tree of 7 brands under Dropbox. Dropbox DocSend Dropbox Dropbox Dash Dropbox Paper Dropbox Sign 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: 6 of 32.

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 →

🇺🇸 DocSend and other American brands

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

All American brands and who owns them →

Frequently asked questions

Who is the parent company of DocSend?

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

Is DocSend American?

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

Is DocSend still owned by Dropbox?

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

Sources (1) & 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.

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