Form FWP Free Writing Prospectus Files Dataset

The Form FWP Files Dataset is a submission-level mirror of every Form FWP (Free Writing Prospectus) filing on EDGAR, packaged by calendar month as {YYYY}/{YYYY-MM}.zip archives. One record corresponds to a single EDGAR FWP accession — identified by its 18-character accession number — and bundles the submission's metadata.json header, the primary free writing prospectus document (almost always an HTML file wrapped in EDGAR's SGML <DOCUMENT> envelope), and any non-image companion attachments carried on the same submission (most commonly a companion PDF). Form FWP is the EDGAR submission type used to file supplemental offering communications under Securities Act Rules 163 and 433 — structured-note term sheets, pricing supplements, road-show decks, investor presentations, and other written offers tied to a registered offering. The dataset is filed by issuers, underwriters, dealers, and other offering participants — Morgan Stanley Finance LLC, HSBC USA, JPMorgan Chase Financial, Citigroup, Barclays, UBS, Goldman Sachs, Royal Bank of Canada, and Bank of Montreal are among the highest-volume filers — and coverage begins on December 1, 2005, the effective date of the Securities Offering Reform that created Form FWP, and runs through the most recent monthly refresh.

Dataset APIs

Dataset Files

What This Dataset Contains

Each record in the dataset corresponds to a single EDGAR submission of Form FWP, the submission type used to file a free writing prospectus under Securities Act Rules 163 and 433. A free writing prospectus is any written communication (including electronic communications, term sheets, fact sheets, road show materials, investor presentations, or press-release-style marketing copy) that constitutes an offer to sell, or a solicitation of an offer to buy, securities in connection with a registered offering, and that does not itself qualify as a Section 10 statutory prospectus. Rule 433 imposes both filing and legending obligations: the communication must generally be filed with the SEC no later than the date of first use, and it must bear a conspicuous legend identifying the registration statement on file and directing investors to the statutory prospectus. The FWP submission is therefore not a self-contained offering document in the Section 10 sense; it is a supplemental, registered-offering-linked communication whose legal context is defined by an underlying effective or pending registration statement (typically an S-3, S-1, F-3, or a shelf takedown prospectus supplement on Form 424).

The dataset covers the entire FWP filer population on EDGAR from December 1, 2005 — the effective date of the Securities Offering Reform (Release No. 33-8591) that introduced the form — through the current refresh. Records are distributed as monthly ZIP containers following the YYYY/YYYY-MM.zip pattern. Each container holds one folder per accession; inside every folder the metadata.json manifest sits alongside the mirrored primary document (HTML) and any companion PDF. Graphic attachments (JPG, GIF) and the synthetic EDGAR "Complete submission text file" SGML bundle are enumerated in metadata.json but not mirrored into the archive, so the manifest still preserves a full inventory of the original submission even when the bytes are not carried along.

Content Structure of a Single Form FWP Record

The accession-number folder

Inside each monthly archive, every record is a dedicated folder named with the dash-stripped accession number (for example 000183988225042120 for accession 0001839882-25-042120). The folder name is the 18-digit EDGAR accession number with dashes removed. The 10-digit prefix is the zero-padded CIK of the filing agent or filer; the next two digits are the two-digit year of assignment; and the final six digits are that filer's per-year sequence counter. The folder name therefore encodes the filer but not the subject issuer; recovering the subject requires reading metadata.json.

Every record folder is composed of three layered content blocks:

1. EDGAR submission metadata in metadata.json: accession number, filing timestamp, filer and subject entities, EDGAR cross-links, and a manifest of every document in the original submission (documentFormatFiles[]).
2. The primary FWP document: nearly always a single .htm file mirrored from EDGAR under its original filename (typically containing an _fwp token, e.g. tm2521972d92_fwp.htm, ea0251222-01_fwp.htm, msf9527_fwp-23052.htm). The HTML body is wrapped in EDGAR's SGML <DOCUMENT> envelope exactly as transmitted.
3. Optional companion attachments: most commonly a PDF rendering of the same free writing prospectus, sitting alongside the HTML with a parallel filename (e.g. tm2521972-92_fwp.pdf next to tm2521972d92_fwp.htm). Non-mirrored companions (graphic images, the synthetic .txt submission bundle) remain referenced only by URL inside metadata.json.

Together these layers allow a record to be interpreted structurally (via the metadata manifest), read as a document (via the HTML or PDF body), and rejoined to its parent registration statement (via the fileNo on the subject entity and the Rule 433 legend printed on the first page of the document).

metadata.json

The JSON header carries submission-level fields common to every record and entity-level blocks describing each party to the filing. Key fields observed:

• formType: always "FWP" in this dataset.
• accessionNo: dashed 18-character accession number, serving as the primary key.
• filedAt: ISO-8601 timestamp including the filer's local offset (e.g. 2025-07-31T19:03:16-04:00), used as the filing date.
• description: short boilerplate identifying the filing as made under Rules 163/433.
• linkToFilingDetails: absolute URL of the primary document on EDGAR (the same file mirrored into the folder).
• linkToTxt: URL of the EDGAR "Complete submission text file" SGML bundle; not mirrored into the zip.
• linkToHtml: URL of the EDGAR filing-index page (...-index.htm).
• linkToXbrl: consistently an empty string, since free writing prospectuses are not within the XBRL/iXBRL tagging regime.
• documentFormatFiles[]: ordered manifest of every file in the original submission. Each entry has sequence, type (e.g. "FWP", "GRAPHIC", or a blank for the synthetic complete-submission bundle), description (the filer's free-text label such as "FREE WRITING PROSPECTUS", "FACT SHEET", or "FREE WRITING PROSPECTUS TO PRELIMINARY PRICING SUPPLEMENT NO. 9,527"), size (byte count as a string), and documentUrl. Only FWP-type documents (and occasional HTML/PDF supplements) are mirrored into the folder; GRAPHIC entries and the .txt bundle are referenced by URL only.
• dataFiles[]: always empty for FWPs.
• seriesAndClassesContractsInformation[]: empty unless the FWP relates to an investment-company series/class offering.
• entities[]: usually two objects representing the same or related legal entities under two roles. Each carries cik, companyName (suffixed with "(Filed by)" or "(Subject)"), type ("FWP"), sic (four-digit SIC with its textual description), irsNo, stateOfIncorporation, fiscalYearEnd in MMDD form, and an optional tickers[] array when listed tickers exist. The "(Subject)" variant additionally carries act (typically "34"), fileNo (the EDGAR file number of the registration statement the FWP relates to, e.g. 333-277211, 333-275587-01), and filmNo. For self-filed FWPs the filer and subject CIKs match; for FWPs filed by an underwriter or other affiliate they differ.

The SGML <DOCUMENT> wrapper

Every mirrored HTML document retains its EDGAR SGML envelope ahead of the HTML content. The header block carries five pseudo-tags that mirror the documentFormatFiles[] entry for the same file:

          1
          <DOCUMENT>
        

          2
          <TYPE>FWP
        

          3
          <SEQUENCE>1
        

          4
          <FILENAME>msf9527_fwp-23052.htm
        

          5
          <DESCRIPTION>FREE WRITING PROSPECTUS TO PRELIMINARY PRICING SUPPLEMENT NO. 9,527
        

          6
          <TEXT>
        

          7
          <HTML>... body of the free writing prospectus ...</HTML>
        

          8
          </TEXT>
        

          9
          </DOCUMENT>
        

<TYPE> and <SEQUENCE> align with the JSON manifest, <FILENAME> matches the on-disk name, and <DESCRIPTION> matches the description field. The HTML body proper sits between <TEXT> and </TEXT>; the envelope closes with </DOCUMENT>. Consumers that want clean HTML must strip this outer SGML shell; consumers that want to reason about submission structure can parse the pseudo-tags as first-class metadata.

The Rule 433 opening legend

Inside the HTML body, the first substantive content is the mandatory Rule 433 legend, the structural signature of an FWP. It is typically right-aligned at the top of the first page and names the Securities Act rule, the registration statement number(s) under which the offering is registered, and the date of first use. Typical forms observed in the dataset:

          1
          Filed Pursuant to Rule 433
        

          2
          Registration Nos. 333-283057 and 333-163855
        

          3
          July 1, 2025
        

          1
          Free Writing Prospectus to Preliminary Pricing Supplement No. 9,527
        

          2
          Registration Statement Nos. 333-275587; 333-275587-01
        

          3
          Dated August 1, 2025; Filed pursuant to Rule 433
        

          1
          Free Writing Prospectus
        

          2
          Registration Statement No. 333-277211
        

          3
          July 31, 2025
        

          4
          Filed Pursuant to Rule 433
        

          5
          (To Prospectus dated February 21, 2024, Prospectus Supplement dated February 21, 2024 and Stock-Linked Underlying Supplement dated February 21, 2024)
        

The string "Filed Pursuant to Rule 433" appears once in the primary document and is a reliable anchor for extracting the legend. The registration numbers printed here match the fileNo on the "(Subject)" entity in metadata.json, and they typically also appear encoded in the URL path of in-body links back to the underlying prospectus supplement, giving three independent encodings of the same registration that can be used to join FWPs to their parent shelf.

The body of the free writing prospectus

The middle of the document is the actual supplemental communication. Its layout varies by issuer archetype, but every FWP body identifies the issuer and the offering, provides the supplemental terms or marketing content, and precedes the closing investor-notice legend. The archetypes observed in the dataset, in order of volume, are:

• Structured-note term sheets. The dominant archetype (Morgan Stanley Finance LLC alone accounts for 638 of 1,823 folders in the 2025-07 sample; other high-volume filers include HSBC USA, JPMorgan Chase Financial, Citigroup Global Markets, Barclays Bank, UBS, Goldman Sachs, Royal Bank of Canada, and Bank of Montreal). The body is laid out as HTML tables that open with a headline describing the note (e.g. "Worst-of RTY and SX5E Market-Linked Notes due August 31, 2028", "Contingent Income Auto-Callable Securities due August 11, 2028") and then enumerate structured fields row-by-row: Issuer, Guarantor, Underliers / Underlying shares, CUSIP, ISIN, Pricing date, Original issue date, Maturity date, Participation rate, Buffer, Downside threshold, Contingent quarterly payment, Determination dates, Call dates, Estimated value on the pricing date, and related payoff mechanics. These term sheets typically embed a hyperlink back to the related preliminary 424(b)(2) pricing supplement on EDGAR.
• Non-structured-product supplemental communications. Non-shelf issuers embed whatever supplemental material accompanied the marketing effort: investor presentations with slide-style HTML layouts, fund-change notices with mapping tables (old CUSIP to new CUSIP, expense ratios, trailing returns), merger-related investor Q&A, road-show decks, or press-release-style marketing copy.
• Fact sheets and summary term sheets for corporate bond, preferred stock, or convertible offerings that elaborate on specific offering terms ahead of pricing.

The Rule 433 closing legend

The body concludes with the mandatory closing legend directing investors to the registration statement. Its text is substantively identical across filers:

The issuer has filed a registration statement (including a prospectus) with the SEC for the offering to which this communication relates. Before you invest, you should read the prospectus in that registration statement and other documents the issuer has filed with the SEC for more complete information about the issuer and this offering. You may get these documents free by visiting EDGAR on the SEC website at www.sec.gov. Alternatively, the issuer will arrange to send you the prospectus if you request it by calling [issuer-specific contact].

The issuer-specific contact (toll-free number or underwriter desk) is the main variable portion. Presence of this block is a structural hallmark of a compliant FWP and, with the opening legend, bounds the substantive body of the document.

Companion PDF attachments

A subset of records ships with a PDF rendering of the same free writing prospectus. In the 2025-07 sample, 170 of 1,823 records include a PDF next to the HTML, carrying a real %PDF-1.x header. The PDF is typically either a publication-quality typeset rendering of the same content (used by shelf term-sheet programs where precise formatting matters) or a scanned/typeset document that supplements a simpler HTML wrapper (used by investor presentations). Filers vary in whether they include both formats, HTML only, or, rarely, PDF only.

Excluded or separately referenced content

The dataset packaging excludes:

• Image attachments (GRAPHIC entries typed JPG, GIF, and similar). They are enumerated inside documentFormatFiles[] but not mirrored into the zip; <IMG SRC="..."> references inside the HTML body may therefore dangle.
• The synthetic EDGAR "Complete submission text file": the all-in-one .txt SGML bundle of the submission. It is referenced via linkToTxt and documentFormatFiles[] but not mirrored. Its content is reconstructable from the individual documents that are mirrored.
• The parent registration statement (S-3, S-1, F-3) and any related prospectus supplement (424B2, 424B5) referenced by the FWP. These are separate EDGAR filings with their own accession numbers; the FWP record points back to them via the subject entity's fileNo and via in-body hyperlinks and legend text, but does not embed them.

Content and format stability over time

The core structural elements of an FWP (identification of the registration statement, the Rule 433 opening legend, and the investor-notice closing legend) have been stable since Rule 433 took effect on December 1, 2005, which is also the dataset's earliest coverage date. Within that window, the meaningful shifts affecting record shape are:

• Rise of structured-note term-sheet dominance. Following the 2008-2009 financial crisis, large broker-dealer shelf programs increasingly used FWPs to file per-note preliminary term sheets referencing shelf-registered medium-term-note programs. From roughly 2010 onward, a large share of FWP volume takes the form of short, highly templated term-sheet tables, which continues to dominate today's volume.
• FINRA Rule 2210 and estimated-value disclosures. Over time, risk-factor summaries, estimated-value-on-the-pricing-date disclosures, and issuer-credit-risk callouts have been added to structured-note FWPs. Estimated-value disclosures in particular became standard in structured-note term sheets after 2013.
• Payoff-archetype vocabulary expansion. The vocabulary of structured-note FWPs expanded across the 2010s to cover worst-of baskets, auto-callable notes, contingent-coupon notes, and market-linked certificates of deposit, with corresponding new fixed-label rows in term-sheet tables.
• Format migration from PDF-only to HTML-native. In 2005-2009, a larger share of FWPs were filed as PDFs, reflecting the practice of filing scanned road-show decks and typeset investor presentations. Over time, HTML-native filings have become the norm, especially for structured-note term sheets.
• Disclosure-automation-generated HTML. Later filings increasingly include platform-generated HTML; Workiva/Wdesk-produced documents carry identifying HTML comments (<!-- Document created using Wdesk -->, <!-- Copyright 2025 Workiva -->), and certain shelf-program filings show vendor-specific tooling signatures (e.g. the QES marker <!-- QES ... --> seen on Morgan Stanley filings).
• Stable SGML envelope. Throughout the entire 2005-present window, the outer <DOCUMENT>/<TYPE>/<SEQUENCE>/<FILENAME>/<DESCRIPTION>/<TEXT> header has remained the EDGAR-canonical way of framing each document, and it is preserved intact in this dataset.

The content requirements imposed by Rule 433 itself (legend text, linkage to a specific registration statement, filing timeliness) have not changed materially during the dataset window.

Interpretation and extraction notes

• Filer vs. subject distinction. The two-entry entities[] block distinguishes who filed the FWP from whom the FWP is about. For most shelf issuers (Morgan Stanley Finance LLC, HSBC USA) the two entries share the same underlying CIK with the role tags "(Filed by)" and "(Subject)". For underwriter-filed FWPs the CIKs differ, and the "(Subject)" CIK is the correct issuer identifier for joins. The fileNo and filmNo fields appear only on the "(Subject)" variant.
• Joining to the parent registration statement. The fileNo on the "(Subject)" entity, the registration numbers printed in the Rule 433 legend, and the URL paths inside in-body hyperlinks to the related 424(b) prospectus supplement are three independent encodings of the same underlying shelf or standalone registration. Any of them can be used to rejoin an FWP to its parent filings.
• Accession folder encodes the filer, not the issuer. The 10-digit prefix of the folder name is the filing-agent CIK, which may or may not match the issuer. Always consult entities[] rather than parsing the folder name to identify the subject issuer.
• Image references may dangle. HTML bodies may include <IMG SRC="..."> references to image files that were filed as GRAPHIC attachments and are not mirrored into the zip. For most FWPs (especially structured-note term sheets), images are branding glyphs or payoff diagrams and are non-substantive; for image-heavy investor presentations, their absence can remove meaningful content. The PDF companion, when present, is usually the best fallback for image-dependent filings.
• Filer-authored descriptions. The description values in documentFormatFiles[] and the SGML <DESCRIPTION> tag are free-text and reflect the filer's labelling conventions. They are often, but not always, literally "FREE WRITING PROSPECTUS"; Morgan Stanley, for example, emits long descriptions that cross-reference a specific preliminary pricing supplement number.
• Filename conventions are not standardized. A _fwp token in the filename is the most common convention, but some issuers use form-aware filenames (e.g. Morgan Stanley's _424b2- embedded in an FWP-type submission) that reference the related prospectus supplement rather than the FWP itself. Identifying the primary FWP body should be done by cross-referencing documentFormatFiles[].type == "FWP" and the SGML <TYPE>FWP header rather than by filename pattern.
• Amendments. Form FWP does not have a practical amendment variant; amendments and restatements are handled by filing a superseding FWP under a new accession number, which appears as an independent record in the dataset.
• One record, one accession. Even when a single offering involves multiple sequential term-sheet FWPs (common for structured-note programs issuing daily or weekly), each FWP submission is a separate record with its own accession folder. Joining them into an offering-level view requires grouping on the subject entity's fileNo plus issuer CIK plus an offering title extracted from the HTML body.

Who Files or Publishes This Dataset, and When

Each record is a single Form FWP submission on EDGAR transmitting a free writing prospectus — a written offering communication used outside the statutory prospectus in connection with a registered offering (or a WKSI pre-filing communication under Rule 163). The filer is the party that used or caused the communication to be used, which may or may not be the issuer. Filers fall into three populations under Rules 163, 164, and 433 of the Securities Act.

Issuers in a registered offering

The largest group is the issuer conducting a registered offering, including:

• domestic Exchange Act reporting issuers running follow-ons, shelf takedowns, or MTN/structured-note programs off an effective S-3, F-3, S-1, or F-1
• well-known seasoned issuers (WKSIs, as defined in Rule 405) using the automatic shelf and Rule 163 regime
• foreign private issuers offering off F-3 or F-1
• asset-backed issuers, sponsors, or depositors filing collateral term sheets and computational materials off SF-3 or SF-1
• BDCs, closed-end funds, and registered REITs in public offerings
• corporate debt issuers filing final term sheets and pricing supplements for individual shelf takedowns

Offering participants (underwriters, dealers, selling securityholders)

Rule 433 requires filing by "any other offering participant" whose use of an FWP triggers filing. This includes:

• investment banks and broker-dealers acting as underwriters or initial purchasers, when they prepare their own marketing materials (road-show decks, sales force talking points, retail-targeted structured-note term sheets)
• ABS dealers distributing collateral tapes or loan-level data
• selling securityholders in registered resales who disseminate written solicitation materials beyond the base prospectus

A participant-prepared FWP that merely duplicates or is derived from the issuer's prospectus or a previously filed FWP does not trigger a separate filing. Materially different participant content ("bank's view" marketing pieces, independent projections) must be filed by that participant.

WKSIs making Rule 163 pre-filing communications

Under Rule 163, a WKSI may make written offers before a registration statement is filed, provided the writing is treated as an FWP and filed promptly upon filing of the related registration statement. These pre-filing communications are a narrow but distinct slice of the FWP population.

When the record is created or required

The triggering event is the use of a written communication that (a) constitutes an offer to sell or solicitation of an offer to buy under Section 2(a)(3), (b) relates to a registered offering (or a Rule 163 pre-filing WKSI communication), and (c) falls outside the Section 10(a) or Section 10(b) prospectus. Section 5(d) of the Securities Act, together with Rules 164 and 433, permits written offers beyond the statutory prospectus; each such permitted writing is a candidate FWP. Rule 405 defines "free writing prospectus" to include electronic communications, graphics, recorded audio/video, and broadly disseminated emails or websites.

Under Rule 433(d), an FWP must be filed no later than the date of first use — the first date the communication is conveyed or made available to any offeree, by email, website posting, hand delivery at a road show, or inclusion in a sales package. Timing sub-regimes refine this:

• Issuer FWPs: filed by the issuer no later than the date of first use.
• Offering-participant FWPs: filed no later than the date of first use, but only when distributed "in a manner reasonably designed to lead to its broad unrestricted dissemination" (e.g., public unrestricted website posting). Limited-audience distribution to specific offerees generally does not trigger filing, though Rule 433(g) requires retention for three years after last use.
• Electronic road shows: a written road show is an FWP, but a bona fide electronic road show for a common equity or convertible offering need not be filed if at least one version is made readily available without restriction to any potential investor.
• Debt pricing term sheets (MTN and structured notes): Rule 433(d) permits final pricing term sheets for debt securities off a shelf to be filed by the second business day after the earlier of first use or pricing.
• ABS informational and computational materials: filed under the Regulation AB / Rule 433 framework, generally no later than first use.
• Rule 163 WKSI pre-filing communications: filed promptly upon the filing of the related registration statement.

Rule 433(c)(2)(i) requires every FWP to contain a prescribed legend stating that the issuer has filed a registration statement with the SEC and directing investors to access the registration statement, prospectus, and other filed documents, including a toll-free number to obtain the prospectus from the issuer or any underwriter.

Regulatory anchor and historical scope

The FWP regime was created by the SEC's Securities Offering Reform (Release No. 33-8591), adopted June 29, 2005 and effective December 1, 2005. The operative provisions are Section 5(d) of the Securities Act, Rule 405 (definition of FWP and issuer categories), Rule 163 (WKSI pre-filing offers), Rule 164 (availability of Rule 433 post-filing and a cure for immaterial or unintentional non-compliance), and Rule 433 (filing, legend, and retention conditions). EDGAR Form Type FWP is used for all Rule 433 filings, including Rule 163 pre-filing and Rule 164 post-filing communications; amendments use FWP/A. Form FWP has existed only in electronic EDGAR form since December 1, 2005 — there is no paper or microfiche predecessor; before the 2005 reforms, written offering communications outside the statutory prospectus were generally barred by Section 5(b)(1) except through narrow exceptions such as Rule 134.

Important distinctions

Issuer FWPs vs. offering-participant FWPs. Both are Form FWP submissions but reflect different trigger logic. Issuer use triggers filing whenever the issuer or its agent uses a written offering communication. Participant use triggers filing only when the participant's communication is broadly disseminated in a way that converts it from a limited-audience communication (no filing) into a public offering document (filing). The EDGAR filer CIK identifies which role generated the record.

WKSI pre-filing communications vs. post-filing FWPs. Rule 163 pre-filing communications are available only to WKSIs and are permitted before any registration statement exists; they must be filed as FWPs promptly once the registration statement is filed. Post-filing FWPs under Rule 164/433 are available to a broader set of issuer categories (subject to Rule 405 eligibility) and are filed by first use.

Communications that are not FWPs. Safe-harbor communications are not FWPs and are not filed on Form FWP: Rule 168 (ordinary-course factual and forward-looking information by reporting issuers), Rule 169 (ordinary-course factual information by non-reporting issuers), Rule 134 (tombstone notices), and Rule 135 (limited-content notices of a proposed offering). Oral road-show communications are also excluded; only written, graphic, or recorded communications qualify.

Ineligible issuers. Under Rule 405 and Rule 164, "ineligible issuers" (recent violators, most shell companies, blank-check companies, penny-stock issuers, and issuers in certain enforcement postures) may not use an FWP. Form FWP should not appear for these issuers during ineligibility.

Relationship to 424 prospectuses. An FWP must relate to a filed registration statement (or one being filed for Rule 163 WKSIs) and supplements rather than replaces the Section 10 prospectus. Final pricing in a shelf takedown is ordinarily carried on a Rule 424(b) supplement; the FWP covers marketing communications, supplemental terms, or preliminary pricing material around the 424 filing. Records in this dataset almost always pair with a 424B and an underlying Form S-3/Form F-3/Form S-1/Form F-1/SF-3 under the same issuer CIK.

Entities outside the FWP regime. Form FWP is not used for offerings outside the registered public offering framework: Rule 506 private placements, Regulation S offshore offerings, Regulation A (Form 1-A and Rule 255 testing-the-waters), Regulation Crowdfunding, and exempt municipal offerings. Registered investment companies governed by Rule 482 and Rule 498 advertising regimes do not use Form FWP, except that BDCs and certain closed-end funds conducting registered offerings do.

Amendments and late filings. Form FWP/A is used to amend a prior FWP. Rule 164(b) provides a limited cure for unintentional or immaterial filing failures, so late-filed FWPs appear in the dataset where the filer relies on the cure.

How This Dataset Differs From Similar Datasets or Filings

Form FWP sits in the Securities Act offering-communications family. To decide whether the FWP dataset is the right source, the practical comparisons are the 424 variants it accompanies, the registration statements it references, the Rule 134 notices and pre-filing communications that sit just outside Rule 433, the Rule 497 fund analogues, and two internal splits within FWP itself (issuer vs. offering-participant, pricing term sheet vs. marketing material).

Rule 424 prospectus supplements (424A, 424B1-B8, 424H)

Often filed the same day as the FWP for the same takedown, which is the main source of confusion.

• Rule 424 is the legally operative statutory prospectus; FWP is by definition not a statutory prospectus and cannot replace it.
• 424 content is standardized: definitive terms, use of proceeds, plan of distribution, full risk factors, Section 10 disclosure.
• FWP content is whatever Rule 433 permits beyond that: investor decks, preliminary pricing, structured-note payoff diagrams, redlined term sheets, Q&A.
• For binding offering terms, use 424. For marketing and pricing communications around the deal, use FWP. The two are complementary, not substitutable, and are typically joined on CIK plus file number.

S-1, S-3, F-1, F-3 and other registration statements

Every FWP presupposes an effective (or, narrowly, pending) registration. S-1/F-1 are long-form; S-3/F-3 are short-form shelves for seasoned issuers.

• Cadence: one registration (amended as needed) versus many FWPs against the same shelf. A single large structured-notes S-3 can generate thousands of FWPs.
• Unit of observation: the registration statement is the program; each FWP is a takedown-level communication.
• Purpose: registration statements are drafted for legal sufficiency; FWPs are drafted for targeted communication about a specific tranche or audience.
• The mandatory FWP legend points readers back to the base prospectus, so the datasets are routinely joined; neither substitutes for the other.

Rule 134 notices (tombstone advertisements)

Closest in spirit (both are offering communications tied to a registered deal) but structurally different.

• Rule 134 is content-restricted to factual identifying information and is deemed not to be a prospectus; Rule 134 notices are typically not filed on EDGAR.
• FWPs are treated as prospectuses ("free writing" prospectuses), carry far broader permitted content, and must be filed with EDGAR on or before first use in most cases.
• Any offering material containing opinions, forward-looking marketing claims, detailed terms, or payoff descriptions is in FWP, not Rule 134.

Rule 163A and Section 5(d) pre-filing communications; road-show materials

The nearest economic cousins to FWPs, but mostly absent from EDGAR.

• Rule 163A (>30 days pre-filing) and Section 5(d) testing-the-waters materials are generally not filed at all.
• Electronic road shows made publicly available are usually not required to be filed, though issuers sometimes voluntarily file road-show decks as FWPs.
• The FWP dataset captures only the subset of pre-sale marketing that crosses the Rule 433 filing threshold; a large volume of economically similar communications (private road shows, limited-access presentations, testing-the-waters decks) will never appear in any SEC dataset.

Form 497 and 497K (investment-company prospectus supplements)

The fund-world analogue to Rule 424, not to FWP.

• Registered funds do not file FWPs under Rule 433 in the ordinary course; Rule 482 governs fund marketing instead.
• Form 497/497K covers open-end mutual funds, ETFs, and variable products; FWP covers corporate, structured-product, and operating-company offerings.
• Filer populations are largely disjoint. The main fund-adjacent cases in the FWP corpus are closed-end fund IPOs and BDC offerings.
• Treating 497 and FWP as interchangeable misstates both coverage and regime.

Issuer FWPs vs. offering-participant FWPs

Rule 433 distinguishes FWPs prepared by or for the issuer from those prepared by underwriters or dealers. Both are filed as form type FWP and both appear in this dataset.

• Issuer FWPs skew toward company presentations, earnings reconciliations, and issuer-authored structured-product term sheets.
• Underwriter FWPs skew toward pricing indications, dealer marketing, and research-style commentary.
• The split matters for Section 12(a)(2) liability and content analysis, but the dataset exposes it only through filer CIK, not form type. Users needing one side must filter on filer identity.

Pricing term sheets vs. marketing FWPs

Two very different document populations share the FWP form type.

• Pricing term sheets (structured notes, MTNs, shelf tranches) are short, dense, and highly structured, locking in coupon, strike, barrier, maturity, and CUSIP. This is the main public source for U.S. structured-product economics and is amenable to numeric extraction.
• Marketing FWPs (investor-day decks, road-show presentations, Q&A scripts, supplemental risk discussions) are narrative, chart-heavy, and suited to qualitative retrieval rather than structured extraction.
• No form-type field separates them; the split must be inferred from length, content, and issuer program.

Boundary summary

FWP holds the Rule 433 supplemental-communication layer of registered offerings: everything that is a written offer tied to a registered deal but is neither the registration statement, nor the 424 statutory prospectus, nor an exempt Rule 134 notice. It does not carry binding statutory disclosure (424 does), does not carry program-level issuer disclosure (S-1/S-3/F-1/F-3 do), is not comparable to Rule 134 (content-limited, off-EDGAR), and does not overlap with Rule 497 (different regime and filer population). Joined with 424 and the referenced shelf registration on CIK and file number, FWP completes the public documentary record of a registered offering by supplying the marketing-and-pricing layer the other datasets deliberately exclude.

Who Uses This Dataset

Form FWP filings carry the economic terms and marketing materials for structured notes, MTN programs, and registered bond offerings. The dataset is used by a focused set of professionals who each pull specific fields from the record.

Structured-products desks at investment banks

Origination and trading teams use FWPs as the primary window into competitor issuance. They scrape preliminary and final term sheets for coupon formulas, participation rates, caps, buffers, knock-in barriers, strike and observation dates, final valuation dates, underlying baskets (single stocks, ETFs, indices, rates, FX, commodities), and CUSIP or ISIN. The issuer CIK and entities[] array map each note back to the parent and its medium-term-note programs, feeding pricing comparables and shelf-share tracking for autocallables and buffered notes.

Structured-note and fixed-income research analysts

Sell-side and independent analysts build issuance calendars and post-trade recaps from FWPs. They focus on tenor, first-call date, coupon step schedules, contingent-interest features, reference-basket composition, and the Rule 433 legend linking back to the base prospectus. Output is weekly issuance monitors and comparative barrier-level analyses across issuers.

Buy-side portfolio managers in structured credit and derivatives

PMs running structured-credit sleeves, insurance general accounts, and derivatives overlays use FWPs for pre-trade diligence and secondary pricing checks. They read term-sheet cash-flow mechanics, scenario tables, and risk-factor passages. CIK plus the entities[] array lets them consolidate exposure to a parent across finance subsidiaries and issuing vehicles.

Quant researchers and term-sheet data engineers

Quant teams and vendor data engineers treat the corpus as a labelled extraction target. They parse HTML and PDF term sheets for strike dates, observation schedules, autocall triggers, coupon barriers, and underlying tickers. The metadata.json fields (accession number, CIK, filing date, entities[]) anchor each extracted record to the regulatory timeline, supporting NER model training, payoff-classification taxonomies, and issuance time series.

Compliance officers at issuers and underwriters

In-house compliance and new-issue paralegals use FWPs to verify Rule 433 timing (filed no later than date of first use), confirm the mandatory legend pointing to the registration statement and statutory prospectus, and check that the filer CIK matches the approved shelf. They reconcile filed marketing materials against internal cleared drafts and use the archive to evidence timely filing patterns during regulatory inquiries.

Capital markets securities attorneys

Deal counsel benchmark Rule 433 legend wording, risk-factor formulations, and estimated-value, hedging-cost, and conflicts disclosures across peer transactions. When structuring a novel payoff or underlying, they pull analogous FWPs as precedent for payoff description, tax language, and secondary-liquidity warnings.

Regulatory and policy analysts

Market-structure analysts at regulators and self-regulatory bodies aggregate FWPs to track issuance volume, retail penetration of complex products, and the prevalence of features like leveraged participation, worst-of baskets, and contingent coupons. Filing date, form type, issuer CIK, and parsed payoff content feed rulemaking on suitability, estimated-value disclosure, and filing timeliness.

Securities litigators and enforcement counsel

Plaintiff and defense teams in structured-note disputes, arbitrations, and enforcement actions pull the full FWP set for an issuer and program to reconstruct what investors were shown and when. They focus on marketing-deck PDFs, hypothetical performance tables, estimated-value language, and filing timestamps relative to pricing. The entities[] array identifies which underwriter or agent filed each piece.

Academic researchers in finance and law

Faculty studying retail structured products use the corpus as a panel from December 2005 forward. They extract payoff parameters to estimate issue-date fair values versus offered prices, measure disclosure evolution after regulatory guidance, and rank issuer shelf dominance. HTML term sheets, PDF decks, and JSON metadata together support reproducible filing-level panels.

Structured-product data vendors

Vendors feeding wealth platforms and portfolio-reporting systems ingest every accession number, parse primary documents and attachments, and normalize issuer, CUSIP, underlying, coupon and call schedules, maturity, and barriers into their schemas. Coverage back to 2005 enables historical backfill; filing-date and accession-number metadata drives incremental ingestion.

LLM and RAG engineers building offering-document assistants

Teams building retrieval systems for wealth advisers, product specialists, and compliance reviewers index the Rule 433 legend, payoff descriptions, scenario tables, and risk factors so assistants can answer questions like "what is the contingent coupon barrier" or "when is the final valuation date" grounded on the filed document.

Specific Use Cases

The FWP corpus supports a small number of distinctive workflows built around structured-note term sheets, pricing communications, road-show decks, and Rule 433 compliance. Each of the use cases below pins a specific data element to a concrete output.

Structured-note term-sheet extraction and issuance panels

Parse the HTML body of term-sheet FWPs (Morgan Stanley Finance LLC, HSBC USA, JPMorgan Chase Financial, Citigroup, Barclays, UBS, GS, RBC, BMO) to pull the fixed-label rows (Issuer, Underliers, CUSIP, ISIN, Pricing date, Maturity date, Participation rate, Buffer, Downside threshold, Contingent quarterly payment, Determination dates, Call dates, Estimated value on the pricing date) into a tabular panel. Joined to metadata.json.filedAt and the subject-entity fileNo, this powers weekly issuance monitors, autocallable and buffered-note league tables, and barrier-level comparables across issuers.

Pricing term sheet vs. preliminary term sheet diffing

For a given shelf takedown, group FWPs by subject-entity CIK plus fileNo and the offering title extracted from the HTML headline, then order by filedAt. Diff the structured-field rows between the preliminary FWP and the superseding pricing FWP (identifiable by descriptions like "FREE WRITING PROSPECTUS TO PRELIMINARY PRICING SUPPLEMENT NO. 9,527") to capture final coupon, strike, barrier, and CUSIP assignment. The output is a clean pricing-event record that connects the marketed economics to the locked-in terms.

Rule 433 timing and legend compliance review

New-issue compliance teams batch-extract the opening legend from the HTML body (anchored on the string "Filed Pursuant to Rule 433") and compare the printed registration numbers to the subject entity's fileNo in metadata.json, and the legend date to filedAt. Filings with missing legends, stale registration numbers, or first-use dates that precede the filing timestamp are flagged for remediation. The closing investor-notice legend (with the issuer-specific call-in contact) is checked for presence and boilerplate drift across the firm's program.

Road-show deck and investor-presentation retrieval

For IPO, convertible, and corporate-bond deals, filter documentFormatFiles[] for FWP submissions that ship a companion PDF (roughly one in eleven records in the 2025-07 sample) and whose filer description is not a structured-note pricing supplement. The PDFs carry the road-show decks and marketing presentations themselves, keyed by subject CIK and filedAt; they feed precedent libraries for deal counsel drafting peer offerings and litigation teams reconstructing what investors were shown before pricing.

Shelf-program consolidation across finance subsidiaries

Resolve exposure to a parent (Morgan Stanley, JPMorgan, Citigroup) by joining on the "(Subject)" entity's cik and fileNo rather than the accession-folder prefix, which encodes only the filer. Aggregating term-sheet fields up this tree produces per-program issuance counts, underlying-basket frequencies (worst-of RTY/SX5E, single-stock references), and outstanding-notional estimates feeding counterparty-risk and shelf-share dashboards.

Training data for payoff-classification and term-extraction models

Quant and vendor teams use the HTML term sheets, with their stable fixed-label row structure, as labelled examples for NER and payoff-type classifiers (autocallable, contingent-coupon, worst-of, buffered, market-linked CD). The SGML <TYPE>FWP header and documentFormatFiles[] manifest distinguish the primary body from GRAPHIC and synthetic .txt attachments, and metadata.json.accessionNo plus filedAt anchor each training example to the regulatory timeline for reproducible splits and incremental updates.

Dataset Access

Dataset Index JSON API: https://api.sec-api.io/datasets/form-fwp-files.json

Returns dataset metadata (name, description, last updated timestamp, earliest sample date, total records and size, form types, container format, and file types) along with the full dataset download URL and the list of individual monthly containers. Each container entry includes its relative key, size, record count, updated timestamp, and direct download URL. Poll this endpoint to detect which containers changed in the latest refresh and download only those that have been updated.

This endpoint does not require an API key.

Example response:

          1
          {
        

          2
            "datasetId": "1f13365b-9ade-61dd-bbed-8ce3a2988a96",
        

          3
            "datasetDownloadUrl": "https://api.sec-api.io/datasets/form-fwp-files.zip",
        

          4
            "name": "Form FWP Files Dataset",
        

          5
            "updatedAt": "2026-04-22T03:02:37.146Z",
        

          6
            "earliestSampleDate": "2005-12-01",
        

          7
            "totalRecords": 304837,
        

          8
            "totalSize": 20649220010,
        

          9
            "formTypes": ["FWP"],
        

          10
            "containerFormat": "ZIP",
        

          11
            "fileTypes": ["HTML", "PDF", "JSON", "TXT"],
        

          12
            "containers": [
        

          13
              {
        

          14
                "downloadUrl": "https://api.sec-api.io/datasets/form-fwp-files/2026/2026-04.zip",
        

          15
                "key": "2026/2026-04.zip",
        

          16
                "size": 13818783,
        

          17
                "records": 154,
        

          18
                "updatedAt": "2026-04-22T03:02:37.146Z"
        

          19
              }
        

          20
            ]
        

          21
          }
        

Download Entire Dataset: https://api.sec-api.io/datasets/form-fwp-files.zip?token=YOUR_API_KEY

Downloads the complete dataset as a single ZIP archive covering all FWP filings from the earliest sample date (2005-12-01) through the most recent refresh. This endpoint requires an API key.

Download Single Container: https://api.sec-api.io/datasets/form-fwp-files/2026/2026-04.zip?token=YOUR_API_KEY

Downloads one monthly container ZIP instead of the full dataset, which is useful for incremental updates or targeting a specific time range. Container paths follow the YYYY/YYYY-MM.zip pattern and can be enumerated from the dataset index JSON. This endpoint requires an API key.

Frequently Asked Questions

What form does this dataset cover?

This dataset covers Form FWP, the EDGAR submission type used to file a free writing prospectus under Securities Act Rules 163 and 433. It is a supplemental offering communication tied to a registered offering — not the statutory prospectus itself — and it bears a mandatory Rule 433 legend pointing back to the underlying registration statement (typically an S-3, S-1, F-3, or 424(b) prospectus supplement).

What does one record in this dataset represent?

One record is a single EDGAR FWP submission, identified by its 18-character accession number. Each record is stored as a folder — named with the dash-stripped accession number — that contains a metadata.json manifest, the primary FWP document (nearly always an HTML file wrapped in EDGAR's SGML <DOCUMENT> envelope), and any non-image companion attachments carried on the submission, most commonly a companion PDF.

Who is required to file Form FWP?

Three populations file Form FWP under Rules 163, 164, and 433: issuers in a registered offering (including WKSIs, foreign private issuers, asset-backed issuers, BDCs, closed-end funds, and corporate debt issuers running shelf takedowns); offering participants such as underwriters, dealers, ABS distributors, and selling securityholders, when their communications are broadly disseminated; and WKSIs making Rule 163 pre-filing communications, which must be filed promptly once the related registration statement is filed.

When must a free writing prospectus be filed?

Under Rule 433(d), an FWP must be filed no later than the date of first use — the first date the communication is conveyed to any offeree. Debt pricing term sheets off a shelf (MTN and structured-note programs) may be filed by the second business day after the earlier of first use or pricing, and Rule 163 WKSI pre-filing communications are filed promptly upon filing of the related registration statement.

What file formats does the dataset contain?

The dataset is distributed as monthly ZIP containers following the YYYY/YYYY-MM.zip pattern. Inside each container, file types include HTML (the primary FWP document), PDF (companion renderings or investor presentations), JSON (metadata.json per record), and TXT. Graphic attachments (JPG, GIF) and the synthetic EDGAR "Complete submission text file" SGML bundle are referenced in metadata.json by URL but not mirrored into the zip.

How far back does coverage go?

Coverage begins on December 1, 2005, the effective date of the SEC's Securities Offering Reform (Release No. 33-8591) that created Form FWP. There is no paper or microfiche predecessor — before the 2005 reforms, written offering communications outside the statutory prospectus were generally barred by Section 5(b)(1) except through narrow exceptions such as Rule 134.

How does the FWP dataset differ from Rule 424 prospectus supplements?

Form 424 is the legally operative statutory prospectus containing definitive terms, use of proceeds, plan of distribution, and full risk factors; Form FWP is by definition not a statutory prospectus and cannot replace one. FWPs carry the supplemental marketing, preliminary pricing, payoff diagrams, investor decks, and term sheets that sit outside Section 10 disclosure. The two forms are complementary and are routinely joined on CIK plus file number to reconstruct the full documentary record of a registered offering.