DSA Scope GuideEU

Digital Services Act Service Types and Scope

Classify which DSA service category applies before assigning content moderation, marketplace, search, or very-large-service obligations.

Use this page to separate EU recipient scope, mere conduit, caching, hosting, online platforms, marketplaces, online search engines, and VLOP/VLOSE layering.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
5

Structured answer sets in this page tree.

Primary sources
4

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 9, 2026
Overview

The DSA does not apply one identical rulebook to every digital product. It first asks whether an intermediary service is offered to recipients established or located in the Union, then layers duties by service type: mere conduit, caching, hosting, online platform, online platform allowing consumers to conclude distance contracts with traders, online search engine, and very large online platform or very large online search engine.

Section 1

Start with EU recipient scope and intermediary status

Article 2 applies the DSA to intermediary services offered to recipients that have their place of establishment or are located in the Union, regardless of where the provider itself is established. A non-EU provider can therefore be in scope if it enables natural or legal persons in one or more Member States to use the service and has a substantial connection to the Union.

The first scoping record should decide whether the service is an information society service and whether it is one of the three intermediary service types named in Article 3: mere conduit, caching, or hosting. If the product is not an intermediary service, the DSA does not convert the underlying product, transport, accommodation, delivery, consumer-law, product-safety, copyright, privacy, or audiovisual rules into DSA obligations.

  • Record the EU connection: establishment in the Union, targeted Member States, EU language or market targeting, and the evidence of recipients in one or more Member States.
  • Classify each distinct service separately when one product bundles access, infrastructure, storage, marketplace, search, ads, or user-generated content features.
  • Keep the underlying non-intermediary service separate from the intermediary layer that transmits, temporarily stores, or hosts recipient-provided information.
  • Use Article 2 exclusions and related-law carve-outs to avoid treating the DSA as a replacement for GDPR, ePrivacy, consumer protection, product safety, copyright, or audiovisual media rules.
Section 2

Separate mere conduit, caching, and hosting

A mere conduit service transmits recipient-provided information in a communication network or provides access to a communication network. A caching service also transmits recipient-provided information but temporarily stores it automatically and intermediately to make onward transmission more efficient or secure. A hosting service stores information provided by, and at the request of, a recipient of the service.

The classification matters because the DSA liability exemptions and due-diligence duties build from this base. Mere conduit and caching analysis focuses on transmission and technical storage conditions. Hosting adds notice-and-action mechanisms, statement-of-reasons duties for certain restrictions, and notification duties for suspicions of serious criminal offences.

  • Use mere conduit for network access or transmission where the provider does not initiate the transmission, select the receiver, or select or modify the information.
  • Use caching for automatic, intermediate, temporary storage that exists only to improve or secure onward transmission and is handled under Article 5 conditions.
  • Use hosting when the provider stores recipient-provided information at the recipient's request, including cloud, web hosting, user accounts, listings, posts, reviews, or uploaded files.
  • Do not assume all hosting is an online platform; online-platform status requires storing and disseminating information to the public and is excluded where public dissemination is only minor and ancillary.
Section 3

Identify online platforms, marketplaces, and search engines as overlays

An online platform is a hosting service that stores recipient-provided information and disseminates it to the public at the recipient's request, unless public dissemination is only a minor and purely ancillary feature. Social networks, content-sharing services, app stores, and platforms where consumers can conclude distance contracts with traders are common examples, but the legal test depends on the service facts.

Marketplaces are not merely any commerce website. The DSA marketplace overlay applies to providers of online platforms allowing consumers to conclude distance contracts with traders. That overlay adds trader traceability, interface design duties for trader information, and consumer information duties when an illegal product or service was offered through the platform. Online search engines are their own intermediary service category and have separate active-recipient and VLOSE designation analysis.

  • For online-platform status, document what recipient-provided information is stored, how it is disseminated to a potentially unlimited public, and whether any public feature is more than minor and ancillary.
  • For marketplace status, document whether consumers located in the Union can conclude distance contracts with traders through the platform.
  • For marketplace duties, keep trader identity, contact, payment-account, register, self-certification, and product/service listing interface records aligned with Articles 30 and 31.
  • For online search engines, keep the query, indexed-result, and active-recipient analysis separate from online-platform logic.
Section 4

Layer duties instead of picking one label

DSA scoping is cumulative. All intermediary providers have baseline duties such as points of contact, terms-and-conditions transparency, and transparency reporting unless an exclusion applies. Hosting services add notice-and-action and statement-of-reasons duties. Online platforms add complaint handling, out-of-court dispute settlement access, trusted-flagger handling, misuse policies, advertising transparency, recommender transparency, and minor-protection duties where the factual triggers exist.

Micro and small enterprise exclusions reduce some online-platform and marketplace obligations, but they do not remove every DSA duty and they do not protect a service that is designated as a very large online platform. For marketplaces, the additional trader-traceability and interface duties are a further layer on top of online-platform status, not a substitute for hosting or platform obligations.

  • Build an obligation matrix with rows for each service and columns for intermediary baseline, hosting, online platform, marketplace, online search engine, VLOP, and VLOSE layers.
  • Mark micro or small enterprise exclusions only against the specific DSA sections they affect, and keep Article 24(3) request-response obligations visible.
  • Keep statement-of-reasons and transparency-database logic tied to hosting or online-platform moderation actions, not to mere conduit or caching services by default.
  • Treat advertising, recommender systems, minors, trader traceability, and illegal-product notifications as feature-triggered overlays within the relevant service category.
Section 5

Check VLOP and VLOSE designation separately

VLOP and VLOSE status is not a self-selected marketing label. The Commission classifies platforms and search engines with more than 45 million users per month in the EU as very large online platforms or very large online search engines and designates services based on user numbers. Designation then triggers the most stringent DSA duties for that designated service.

The user-number record should be service-specific. Article 24 requires providers of online platforms and online search engines to publish average monthly active recipients in the Union at least every six months, and Commission guidance explains that this information is relevant for VLOP and VLOSE designation. Once designated, a service has four months to comply with the VLOP/VLOSE-specific obligations.

Does the DSA treat every hosting provider as an online platform?

No. Hosting means storing recipient-provided information at the recipient's request. Online-platform status adds a further test: the service must also disseminate that information to the public, unless that public dissemination is only minor and ancillary to another service.

When does a marketplace get extra DSA duties?

The marketplace layer applies when an online platform allows consumers to conclude distance contracts with traders. That layer adds trader traceability, interface design for required trader and product information, and duties to inform consumers about illegal products or services in the circumstances covered by Article 32.

What is the DSA VLOP or VLOSE threshold?

The Commission describes VLOPs and VLOSEs as online platforms or search engines with more than 45 million users per month in the EU. Providers must keep service-specific average monthly active recipient numbers because designation depends on the relevant platform or search service.

  • Calculate average monthly active recipients for each online platform or online search engine, not only for the corporate group or app family.
  • Separate registered users, visitors, buyers, sellers, viewers, searchers, bots, and indirect recipients so the active-recipient method matches the service type.
  • If a service approaches or exceeds 45 million monthly EU users, prepare the VLOP/VLOSE layer: systemic-risk assessment, risk mitigation, compliance function, independent audit, data access, non-profiling recommender option where relevant, and public ad repository where relevant.
  • Track Commission designation, revocation, and information-request evidence separately from ordinary online-platform or online-search-engine compliance evidence.
Primary sources

References and citations

digital-strategy.ec.europa.eu
Referenced sections
  • Commission FAQ notes that small and micro-enterprises are exempted from some rules and that VLOPs and VLOSEs have additional obligations.
"Very large online platforms and search engines have additional obligations."
digital-strategy.ec.europa.eu
Referenced sections
  • Commission guidance explains the average monthly active recipient publication requirement and its relevance for VLOP and VLOSE designation.
"average monthly active recipients of the service in the Union"
eur-lex.europa.eu
Referenced sections
  • Articles 24, 33, and 34 to 43 set the active-recipient publication, VLOP/VLOSE designation, systemic-risk, audit, data-access, compliance-function, and transparency layers.
"average monthly active recipients of the service in the Union"
Related guides

Explore more topics

DSA Ads and Recommender Systems: transparency duties, user choice, and evidence
A grounded DSA guide to ad labels, targeting restrictions, recommender parameter disclosure, non-profiling options for VLOPs and VLOSEs, ad repositories, and compliance evidence.
DSA Applicability Test: classify intermediary services, platforms, marketplaces, VLOPs and VLOSEs
A source-grounded EU Digital Services Act applicability test for classifying intermediary services, hosting services, online platforms, marketplaces, VLOPs and VLOSEs.
DSA Article 28 minors protection guide for online platforms
EU Digital Services Act guide to Article 28 minors protection: platform scope, child-safety measures, targeted ads limits, recommender controls, and grounded evidence.
DSA average monthly active recipients: what platforms must publish
A grounded FAQ on average monthly active recipients under the EU Digital Services Act, including publication, EU recipient scope, the 45 million VLOP/VLOSE threshold, and evidence records.
DSA Complaint and Dispute Workflows for Online Platforms
Build DSA complaint, appeal, statement-of-reasons, and out-of-court dispute workflows for online platform moderation decisions.
DSA crisis response for VLOPs and VLOSEs
EU Digital Services Act crisis response guide for VLOPs and VLOSEs: Article 36 Commission decisions, Article 48 crisis protocols, mitigation, governance, requests for information, and records.
DSA Dark Patterns: interface design checks for online platforms
Article 25 DSA guidance for reviewing online platform interfaces for deceptive, manipulative, or choice-distorting design patterns.
DSA Enforcement and Penalties in the EU
How Digital Services Act enforcement works: Commission and Digital Services Coordinator roles, VLOP and VLOSE investigations, fines, periodic penalty payments, and evidence readiness.
DSA illegal content notices: what must be included?
A grounded FAQ on EU Digital Services Act illegal-content notices: Article 16 notice elements, acknowledgement, decision notices, trusted flagger priority, statements of reasons, and records.
DSA Marketplace Trader Traceability FAQ
Answer to what EU Digital Services Act Article 30 requires online marketplaces to collect, verify, display, retain, and evidence for trader traceability.
DSA Marketplace Trader Traceability Guide
EU Digital Services Act guide for online marketplaces collecting, checking, displaying, storing, and evidencing trader traceability information.
DSA notice and action plus statements of reasons guide
A grounded Digital Services Act guide for notice intake, moderation decisions, statements of reasons, DSA Transparency Database submission, complaints, appeals, trusted flaggers, and records.
DSA Notice and Action Workflow for Hosting Services and Online Platforms
A grounded DSA notice-and-action workflow covering notice intake, completeness checks, trusted flaggers, decisions, user communications, statements of reasons, appeals, and records.
DSA recommender transparency FAQ: Article 27 and VLOP options
What EU Digital Services Act recommender transparency requires: main parameters, user options, VLOP/VLOSE non-profiling choices, and evidence to keep.
DSA researcher data access for VLOPs and VLOSEs
Article 40 DSA guide to vetted researcher data access for VLOPs and VLOSEs: DSC requests, eligibility checks, amendment grounds, confidentiality, security, and evidence records.
DSA service tier classifier for platforms, marketplaces, VLOPs and VLOSEs
Classify a digital service under the EU Digital Services Act as intermediary, hosting, online platform, marketplace, VLOP or VLOSE, with EU recipient-count evidence and obligation outputs.
DSA statement of reasons FAQ
When DSA statements of reasons are required, what they must contain, when online platforms submit them to the DSA Transparency Database, and what appeal records to keep.
DSA statement of reasons log workflow for online platforms
Build a DSA statement of reasons log for moderation decisions, Transparency Database submission, complaint links, retention, and QA controls.
DSA transparency report template fields and cadence
A source-grounded template outline for Digital Services Act transparency reports, covering applicable service tiers, reporting periods, CSV/XLSX format, retention, statement-of-reasons links, and required evidence tables.
DSA Transparency Reporting Obligations by Provider Tier
A grounded guide to EU Digital Services Act transparency reports, active-recipient publication, statements-of-reasons submissions, VLOP/VLOSE reports, templates, cadence, and evidence.
DSA VLOP and VLOSE Risk Assessments and Mitigation Guide
Grounded guide to Digital Services Act systemic risk assessments, mitigation measures, audits, transparency reports, data access, and governance evidence for VLOPs and VLOSEs.
DSA VLOP Audit Pack Workflow: Risk, Mitigation, Audit, and Transparency Records
Build a DSA VLOP or VLOSE audit pack covering Article 34 risk assessments, Article 35 mitigations, independent-audit evidence, transparency reports, data access, and compliance governance.
DSA VLOP Risk Assessment FAQ: Article 34, Mitigation, Audits
What VLOPs and VLOSEs must assess under the EU Digital Services Act, when to reassess, how Article 35 mitigation and annual audit evidence fit together, and what records to keep.
DSA vs DMA Platform Rules
Compare the EU Digital Services Act and Digital Markets Act by scope, designation thresholds, obligations, enforcement, evidence, and practical team ownership.
DSA vs GDPR: online-platform governance and personal-data obligations
Compare the EU Digital Services Act and EU GDPR by scope, ads, recommenders, minors, transparency, complaints, enforcement, and evidence.
DSA vs P2B Regulation: EU platform obligations compared
Compare the EU Digital Services Act with the Platform-to-Business Regulation for platform scope, business-user terms, content moderation, ranking transparency, complaints, enforcement, and evidence.
DSA vs Terrorist Content Online Regulation: notice-and-action vs removal orders
Compare DSA content-governance duties with the EU Terrorist Content Online Regulation removal-order workflow for scope, timing, evidence, authorities, and team ownership.
EU Digital Services Act checklist for platforms and hosting services
A grounded DSA checklist for classifying service tiers, notice-and-action, statements of reasons, complaints, transparency reports, ads, recommenders, trader traceability, VLOP/VLOSE duties, and evidence records.
EU Digital Services Act Compliance Guide
DSA compliance guide for intermediary services, hosting providers, online platforms, marketplaces, and VLOP/VLOSE teams: obligations, controls, and evidence to keep.
EU Digital Services Act FAQ: DSA scope, platform duties, VLOPs, reports, and penalties
Concise EU Digital Services Act FAQ covering intermediary-service scope, active-recipient thresholds, illegal-content notices, statements of reasons, trader traceability, recommender transparency, systemic-risk duties, reporting, penalties, and complaints.
EU Digital Services Act penalties and fines: caps and enforcement roles
DSA penalty caps and enforcement roles: Member State fines, Commission fines for VLOPs and VLOSEs, 1% procedural fines, and 5% periodic penalty payments.
EU Digital Services Act requirements by service tier
Overview of DSA obligations for intermediary services, hosting providers, online platforms, marketplaces, VLOPs and VLOSEs, including notices, complaints, ads, transparency reports, audits, data access and enforcement.
EU DSA deadlines and compliance calendar: application dates, reporting cycles, and VLOP clocks
Calendar view of grounded EU Digital Services Act dates: full application, user-number publication, VLOP/VLOSE designation clocks, statements of reasons, and transparency reporting cycles.
EU DSA Transparency Calendar: reporting, SoR database, AMAR updates
Build a DSA transparency calendar for annual reports, statement-of-reasons database submissions, active-recipient updates, and VLOP/VLOSE audit touchpoints.
EU DSA vs UK Online Safety Act: scope, duties, regulator, and evidence
Compare the EU Digital Services Act and UK Online Safety Act for platform scope, risk assessments, child protection, transparency, regulators, enforcement, and owners.