# EDGAR Filing Document

**Accession Number:** 0001976322
**File Stem:** 0001829126-25-005020
**Filing Date:** 2025-7
**Character Count:** 3846
**Document Hash:** c8f7a846abd2b2114b9854884e7f8e17
**Contains OCR:** False
**Source Format:** 

## Filing Content

## Filing Summary
**0001829126-25-005020.hdr.sgml**: 20250925

**ACCESSION NUMBER**: 0001829126-25-005020

**CONFORMED SUBMISSION TYPE**: CORRESP

**PUBLIC DOCUMENT COUNT**: 3

**FILED AS OF DATE**: 20250711

**FILER**: 

**COMPANY DATA:**
- **COMPANY CONFORMED NAME:** Themes ETF Trust
- **CENTRAL INDEX KEY:** 0001976322

**ORGANIZATION NAME:**
- **EIN:** 000000000

**FILING VALUES:**
- **FORM TYPE:** CORRESP

**BUSINESS ADDRESS:**
- **STREET 1:** 34 EAST PUTNAM STREET
- **STREET 2:** SUITE 112
- **CITY:** GREENWICH
- **STATE:** CT
- **ZIP:** 06830
- **BUSINESS PHONE:** (646) 206-1788

**MAIL ADDRESS:**
- **STREET 1:** 34 EAST PUTNAM STREET
- **STREET 2:** SUITE 112
- **CITY:** GREENWICH
- **STATE:** CT
- **ZIP:** 06830

![](corresp_001.jpg)

July 11, 2025

Raymond Be

Division of Investment Management

Disclosure Review & Accounting Office

100 F Street, N.E.

Washington, D.C. 20549

---

| | |
|:---|:---|
| **Re:** | **Themes ETF Trust (the "<u>Trust</u>")** |

---

**Post-Effective Amendment No. 35 to the Registration Statement on Form N-1A (the "<u>Amendment</u>")**

**File Nos.: 333-271700 and 811-23872**

Dear Mr. Be:

This correspondence responds to the comment received by the undersigned from the staff of the U.S. Securities and Exchange Commission (the "<u>Staff</u>" of the "<u>Commission</u>") with respect to the Amendment relating to the Leverage Shares 2X Long UNH Daily ETF (the "<u>Fund</u>"). For your convenience, your comment is summarized below with the response following the comment. Capitalized terms not otherwise defined have the same meaning as in the Amendment.

&nbsp;&nbsp;&nbsp;&nbsp;1. <u>Comment</u>: Please supplementally explain why making these changes to an existing ETF in the Amendment
as opposed to an amendment adding a new ETF is consistent with the text and policy of Rule 485(a) under the Securities Act of 1933, as
amended (the "1933 Act"). Please explain why you believe this does not provide a competitive advantage over other registrants
that add new series under Rule 485(a) that go effective in 75 days (as opposed to 60 days).

<u>Response</u>: The changes are being made in a post-effective amendment to the registration statement of an existing fund because the post-effective amendment was filed for the purpose of making material changes to an existing series in accordance with Rule 485(a)(1), rather than adding a new series, in accordance with Rule 485(a)(2) under the 1933 Act. It would not be appropriate for an existing series to file under Rule 485(b)(2). A filing pursuant to Rule 485(a)(1) under these circumstances is wholly appropriate and consistent with text and policy of the rule and industry practice. The Trust does not believe that filing under Rule 485(a)(1) provides an unfair competitive advantage over other registrants because the Trust is adhering to the rules promulgated under the 1933 Act and the Staff's pronouncements thereon. The Trust notes that the changes to the registration statement are publicly available for 60 days prior to the effectiveness of the registration statement and that such changes are subject to review by the Staff. Furthermore, we note that Rule 485(a)(1) is available to every registrant and Rule 485(a)(1) is regularly used by registrants to make material changes to registration statements for funds and making such a filing is consistent with long standing, accepted industry practice.

![](corresp_002.jpg)

**KAREN A. ASPINALL ● PARTNER**

11300 Tomahawk Creek Pkwy, Suite 310 ● Leawood, KS 66211 ● p: 949.629.3928

Practus, LLP ● Karen.Aspinall@Practus.com ● Practus.com

If you have any questions regarding the above responses, please do not hesitate to contact me at (949) 629-3928 or Karen.Aspinall@practus.com.

Sincerely,

/s/ Karen Aspinall

Karen Aspinall

Trust Counsel

![](corresp_002.jpg)

**2**