# AdBreak AdBreak (AdBreak.dev) is AI ad break detection for finished video. AdBreak.dev is a B2B service for video publishers. It is not the Kindle jailbreak called AdBreak and not the adBreak() call of Google’s ad placement API. > AdBreak finds where a finished video can take an ad, and returns the time. It does not insert the creative and it does not condition the stream. ## Quick facts - Product: AdBreak (AdBreak.dev) — B2B ad break detection for finished video files. - Input formats: MP4, MOV, and ProRes files, and IMF packages. - Marker outputs: SCTE-35, HLS cues, VMAP, and JSON break records with reason, confidence (0 to 1), and distance to speech. - Subtitles: SRT and WebVTT from speech in the file, translated into 22 languages. - Delivery: HTTP API, S3, FTP, or HTTP pull and return; customer files are deleted after processing. - Pricing: From $0.70 / €0.70 per hour of video, with lower rates at higher monthly volume. - Contact and pilot: [Request a demo and price](https://www.adbreak.dev/en/contact?form=demo), [Request a callback](https://www.adbreak.dev/en/contact?form=callback), or email hello@adbreak.dev. ## What the review does AdBreak reads scene changes, dark frames, speech, silence, loudness, and motion on the file you submit. A break we keep includes a time, a kind of pause, a reason, confidence, and the distance to speech. The same times can leave as SCTE-35, an HLS cue, or VMAP. SCTE-35 markers sit on a frame the player can cut cleanly, unless that alignment is turned off. Your player receives the marker. AdBreak does not prepare HLS or DASH. ## What the review does not do - It does not insert the creative. - It does not condition the stream. - It does not play or sell the ad. - The scene, the objects, and the people describe the moment. They are not a brand-safety certificate. - The public site does not state an accuracy score for the product. Each break carries its own confidence, reason, and distance to speech. ## Subtitles The same reading of the speech writes SRT and WebVTT. If that reading is skipped or empty, there are no subtitle files, and a second reading is not started. Translation is a catalog of 22 languages: en, fr, de, es, it, pt, nl, pl, sv, da, no, fi, cs, ro, el, hu, uk, ru, pt-BR, ja, zh, hi. ## What the picture shows On each stretch of picture, AdBreak names the scene, the objects, and the people, and writes those names on the frame next to the clock, so the time shows what is in the frame. ## Large libraries A single file can be sent by hand. A large library does not have to be sent one file at a time. Originals are pulled from S3, FTP, or HTTP as they arrive, or sent through the HTTP API, and the break record, the markers, and the subtitle files are uploaded back to S3, FTP, or HTTP. Volume does not insert the creative or condition the stream. A person can still accept a break or set it aside before the marker goes out. ## Inputs, rules, and API Inputs: MP4, MOV, and ProRes files and IMF packages. Opening and closing credits and lower-thirds (names and roles at the bottom of the frame) are detected and marked apart from the breaks. An HTTP API sends files and collects results. Break rules are set with presets by program length: minimum confidence, time skipped at the start and the end, the shortest gap between breaks, and the minimum and maximum number of breaks. ## Pricing Pricing starts at $0.70 / €0.70 per hour of video. The rate depends on monthly volume: the more hours a month, the lower the price per hour. No tier breakpoints are published; contact hello@adbreak.dev for volume pricing. ## File handling and security AdBreak does not store customer files: they are deleted after processing. Results are delivered back to the customer’s S3, FTP, or HTTP location. The public site does not claim security certifications. Ask hello@adbreak.dev for written answers before a pilot. ## Languages The website is in English, Russian, German, and French. Those page languages are not the spoken language of a file and they are not the 22-language subtitle catalog. Speech recognition follows the language spoken in the file. If the speech cannot be followed, that check is skipped. It is not guessed. ## Questions ### Does AdBreak play or sell the ad? No. It finds the break and describes it. Your player, or the system that inserts ads into the stream, places the ad. ### What if the program never really pauses? Clean breaks can be few. If you set a minimum, moments that missed the check can be included, and they are labeled. A break is not moved into the middle of a line just to fill the number. ### Can a person turn a break down? Yes. Confidence, the reason, the distance to speech, and the label on a filled-in break are there so an editor can accept it or set it aside before it becomes a marker. ### Will the marker land where the player can cut? SCTE-35 markers sit on a frame the player can cut cleanly, unless you turn that off. HLS and DASH still need your own preparation of the stream. AdBreak does not prepare HLS or DASH, and it does not insert the ad. ### Is the scene description a brand-safety guarantee? No. The frame and the result describe the moment: the scene, the objects, the people, and how far speech sits from the cut. Certification and blocking stay with the brand-safety tools you already trust. ### Which spoken languages can be followed? Speech recognition follows the language spoken in the file and uses the ends of sentences, so a break can leave a line alone. That reading writes SRT and WebVTT, and those subtitles are translated into 22 languages. This website is in English, Russian, German, and French. If the speech cannot be followed, that check is skipped. It is not guessed. ### Can a large library skip the manual upload? Yes. Originals are pulled from S3, FTP, or HTTP, or sent through the HTTP API, and the results are uploaded back the same way. Files are deleted after processing. You still receive break times, markers, and subtitles. The ad is still not inserted. ## Topics in depth ### How ad break detection works on a finished file. AdBreak reads a finished video file the way an editor would: scene changes and dark frames, the end of a spoken line, silence, loudness, and motion. A moment becomes an ad break only when it passes those checks. Each break comes back with a time, the kind of pause, a reason, a confidence, and the distance to the nearest speech. #### What is read in the file - Picture: Scene changes, cuts, dark frames, fades to black, motion, and editing pace. Opening and closing credits are marked on their own. Lower-thirds, the names and roles shown at the bottom of the frame, are detected as well. - Speech: The ends of sentences and gaps in dialogue, so a break never lands in the middle of a line. - Sound: Silence, quiet passages, music changes, and fades. A loud stretch with no real pause does not win over a fade and a silence. #### How a break is kept - A candidate in the middle of a spoken line is moved or dropped. - Heavy motion, a run of fast cuts, or a loud stretch with no pause is set aside. - If a measurement is missing, that check is skipped. A result is never invented to fill the gap. - If you ask for a minimum number of breaks, weaker moments can be included, and they are labeled so an editor can remove them. #### Break rules and presets - A preset holds break rules for each program length, for example up to 30 minutes, 30 to 60 minutes, and longer. - Each length has its own minimum confidence, time skipped at the start and the end, and the shortest gap between breaks. - You set the minimum and maximum number of breaks, and can ask for breaks spread out across the program. - One preset can cover a whole library, or the rules can be set for a single title. #### What you receive for every break | Field | What it tells you | | --- | --- | | Time | The cut, the scene change, or the dark frame itself, not a second before it. | | Placement | Pre-roll, mid-roll, or post-roll. | | Kind of pause | Cut, scene change, or black. | | Reason | Why this moment was kept, in plain words. | | Confidence | The break score scaled from 0 to 1. | | Distance to speech | How many seconds separate the cut from the nearest speech, and whether that is safe. | | Credits and lower-thirds | When opening and closing credits and lower-thirds appear, marked apart from the breaks. | | Markers | SCTE-35, an HLS marker, or VMAP, ready for your player or ad server. | #### Subtitles and scene names from the same review The same reading of the speech writes SRT and WebVTT files and translates them into 22 languages. On each stretch of picture, AdBreak names the scene, the objects, and the people, and writes them on the frame beside the clock, so a person can check a break before the marker goes out. #### What AdBreak does not do - It does not insert, play, or sell the ad. Your player or ad server does that. - It does not prepare HLS or DASH streams. - It does not watch a live broadcast. It reviews finished files. - The scene description is not a brand-safety certificate. #### Does AdBreak use the program guide or the title to choose breaks? No. Breaks come from the picture, the speech, and the sound of the file itself. The name or genre of a show does not say where to cut. #### Can an editor review breaks before they are used? Yes. Each break carries its reason, confidence, and distance to speech, and the marked frames show the clock and the scene, so a person can accept or set aside a break before the marker goes out. #### Which video files can AdBreak read? Finished files such as MP4, MOV, and ProRes, and IMF packages. Originals can be pulled from S3, FTP, or HTTP or sent through the HTTP API. ### SCTE-35 markers, HLS, and VMAP from a finished video. AdBreak turns each ad break it keeps into a marker your systems already understand: SCTE-35, an HLS marker, or VMAP. Subtitles leave as SRT and WebVTT. Originals, including IMF packages, are pulled from S3, FTP, or HTTP or sent through the HTTP API, and results are uploaded back the same way. AdBreak does not insert the ad. #### Delivery formats | Format | What it carries | Typical receiver | | --- | --- | --- | | SCTE-35 | The break time, placed on a frame the player can cut cleanly unless that alignment is turned off. | Playout, server-side ad insertion, packaging you already run | | HLS marker | The break time as a marker in the HLS playlist your workflow prepares. | HLS players and ad insertion services | | VMAP | Pre-roll, mid-roll, and post-roll positions for the title. | Client-side players and ad servers | | Break record | Every break with time, kind of pause, reason, confidence, and distance to speech. | Ad operations, editors, your own systems | | SRT and WebVTT | Subtitles from the same reading of the speech, translated into 22 languages. | Players, localization teams | | Credits and lower-thirds | Times of opening and closing credits and of lower-thirds on screen. | Editors, ad operations | #### How files and results move - One file at a time: A single title can be sent by hand. The reply explains how the markers will reach you. - HTTP API: Send a file, choose a preset of break rules, and collect the results through the HTTP API. - Originals from S3, FTP, or HTTP: AdBreak pulls each original from your S3, FTP, or HTTP location as it arrives, so nobody uploads titles one by one. - Results back to S3, FTP, or HTTP: The break record, the markers, and the subtitle files are uploaded back to S3, FTP, or HTTP. - Input formats: MP4, MOV, and ProRes files, and IMF packages. #### Adding SCTE-35 markers to a library that has none Many archive episodes were finished before ads were inserted into streams, so they carry no SCTE-35 markers at all. AdBreak reads the finished file, keeps the breaks that pass the checks, and writes an SCTE-35 marker for each one. Your playout or ad insertion system receives the marker and places the ad. #### Your systems keep their job - Your ad server or player inserts and plays the ad. - Your packaging prepares HLS or DASH. AdBreak does not. - Your brand-safety tools keep certification and blocking. #### Can AdBreak connect to our media asset management system or offer an API? Yes. AdBreak has an HTTP API to send files and collect results, and it can pull originals from S3, FTP, or HTTP and upload results back. For a media asset management system, tell us how files move today and we will explain how it connects. ### Who uses ad break detection, and for what. Ad break detection is used by teams that own finished video and need to sell ads inside it: FAST channel operators, owners of AVOD back catalogs, broadcasters preparing BVOD and catch-up, and streaming platforms placing mid-rolls. In every case AdBreak returns the break times and markers. The team’s own ad server places the ad. #### What every use case has in common - The input is a finished file, not a live feed. - The output is a time, a reason, a confidence, and a marker: SCTE-35, HLS, or VMAP. - A person can review breaks before markers go out. - A large library can be processed as files arrive, with results over S3 or FTP. ### Ad breaks for FAST channels, from the finished file. FAST channels run on ads, but many episodes and films reach a channel with no ad break markers. AdBreak reviews each finished file, keeps the moments where the story already pauses, and returns break times with SCTE-35 markers before the title goes to playout. Viewers see the ad at a scene change, not in the middle of a line. #### The problem FAST operators face - Titles arrive unmarked: Library content licensed for a FAST channel often carries no SCTE-35 markers, and a program guide is too rough to place a mid-roll. - A timer cuts through scenes: A break every few minutes lands in a line, a joke, or a camera move. Viewers leave, and the ad opens on a broken shot. - Manual marking does not scale: Finding break points by hand means watching every episode in full, and a channel needs many titles. #### How AdBreak prepares FAST content - Each file is read for scene changes, dark frames, the end of spoken lines, silence, and loudness. - Only moments that pass the checks become breaks. Each one has a reason and a confidence. - If the channel needs a minimum number of breaks, extra moments are included and labeled. - Markers leave as SCTE-35, an HLS marker, or VMAP, ready for your playout or ad insertion. - New titles can be processed as they arrive, with results written to S3 or FTP. #### Subtitles in the same review FAST and AVOD platforms often ask for subtitles. The same reading of the speech writes SRT and WebVTT and translates them into 22 languages. #### Does AdBreak insert ads into our FAST channel? No. AdBreak finds and describes the breaks and delivers the markers. Your playout or ad insertion system places the ad. #### Can AdBreak follow the break rules of a FAST platform? You can set a minimum number of breaks, and placements cover pre-roll, mid-roll, and post-roll. Tell us the platform rules you work with and we will explain how they map to the review. ### Turn an unmarked library into ad-ready inventory. Studios, distributors, and archives hold thousands of hours finished long before ads were inserted into streams, so the files carry no ad markers. AdBreak reviews each title and returns natural ad insertion points with SCTE-35, HLS, or VMAP markers, plus subtitles in 22 languages, so the catalog can be licensed to AVOD and FAST platforms. #### Why old catalogs are hard to sell with ads - Archive episodes rarely carry SCTE-35 markers. - Act breaks from the original broadcast are not always where a streaming platform wants a mid-roll. - Marking a catalog by hand means watching every title. #### What a catalog gets from AdBreak - Break times per title: Pre-roll, mid-roll, and post-roll positions, each with a reason, a confidence, and the distance to speech. - Markers platforms accept: SCTE-35, an HLS marker, or VMAP, delivered with the title. - Subtitles for new markets: SRT and WebVTT from the speech in the file, translated into 22 languages. - Scene names for review: The scene, the objects, and the people on each stretch of picture, so an editor can check a break quickly. #### Processing the whole library You do not have to send titles one by one. Files can be processed as they arrive, and results are written to S3, FTP, or a similar drop. A person can still accept or set aside any break before the markers go to a platform. #### We have no rights to some titles in our archive. Can we still send them? Send only files you have the rights to mark. The pilot starts with titles you control. ### Ad break markers for broadcasters, before playout and for BVOD. Broadcasters receive files without markers and publish the same programs to BVOD and catch-up services. AdBreak reviews the finished file before it goes to air or online and returns break times with SCTE-35 markers placed on a frame the player can cut cleanly. It is a review of the file, not a live switch. #### Where it fits in a broadcast workflow - Before playout: When a file arrives without markers, mark it before it goes to air. - BVOD and catch-up: Place mid-rolls in the on-demand version at moments where the story already pauses. - Ad operations review: Replace a long manual watch with a short list a person can confirm. #### What stays with your systems - Live switching and playout automation stay with your broadcast systems. - Your ad insertion places the ad. AdBreak does not insert it. - HLS or DASH preparation stays with your packaging. #### Languages The website is in English, Russian, German, and French. Speech recognition follows the language spoken in the file, and subtitles are translated into 22 languages. #### Does AdBreak work on a live broadcast? No. AdBreak reviews finished files. It does not watch a live broadcast or act as a live switch. ### Mid-roll ad breaks that keep the story whole. Streaming and OTT platforms with an ad tier need mid-rolls that do not interrupt a line or a scene. AdBreak finds ad insertion points where the story already pauses and keeps every break away from speech. Each break comes with a reason and confidence and leaves as VMAP, SCTE-35, or an HLS marker for your ad server. #### Why placement matters on an ad tier - A mid-roll in the middle of a line breaks the scene and opens the ad on a broken shot. - A fixed timer ignores the story. - Ad operations need a reason they can check, not just a time. #### What your team gets - Speech stays whole: Every break says how far the nearest speech sits from the cut, and whether that distance was safe. - A reason for every break: Scene change, dark frame, end of a sentence, or silence, with a confidence from 0 to 1. - Markers for your stack: VMAP for players, SCTE-35 or an HLS marker for server-side insertion. #### Can we control how many mid-rolls a title gets? You can ask for a minimum number of breaks. If the program has fewer clean pauses, extra moments are included and labeled, so your team can remove them. ### Ad break detection for large libraries. A large library does not have to be sent one file at a time. AdBreak pulls originals from S3, FTP, or HTTP, or receives them through the HTTP API, reviews each file, and uploads the break record, markers, and subtitles back. AdBreak does not store your files: they are deleted after processing. #### How large libraries are handled - Files picked up as they arrive: New titles enter on their own from S3, FTP, or HTTP. Nobody uploads them one by one. - Masters as you deliver them: IMF packages, MP4, MOV, and ProRes files are accepted as originals. - Results back to your storage: The break record, SCTE-35, HLS or VMAP markers, and SRT and WebVTT subtitles are uploaded back to S3, FTP, or HTTP. - One set of rules for the library: A preset sets the break rules for each program length, so every title follows the same rules. - People stay in control: An editor can accept or set aside any break before the marker goes out. #### File handling and content protection AdBreak does not store your files. Each file is processed and then deleted. Ask us before a pilot, and we will answer your security questions in writing. - Files are not stored: they are deleted after processing. - Originals are pulled from your S3, FTP, or HTTP location, so nobody sends copies by hand. - Results are uploaded back to S3, FTP, or HTTP. - Ask us about confidentiality terms before a pilot. #### Start with a pilot Begin with a few titles you have the rights to mark. You see the breaks, the reasons, the markers, and the subtitles on your own content before connecting a library. Pricing starts at $0.70 / €0.70 per hour of video and goes down at higher monthly volume. #### Does volume change what AdBreak does? No. At any volume AdBreak returns break times, markers, and subtitles. It does not insert the ad or prepare the stream. #### Do you keep our files? No. AdBreak does not store your files. They are deleted after processing, and the results are uploaded back to your S3, FTP, or HTTP location. ### Pricing: from $0.70 per hour of video. AdBreak is priced per hour of video, from $0.70 / €0.70 per hour. The rate depends on your monthly volume: the more hours you send each month, the lower the price per hour. Contact us for volume pricing. The usual first step is a pilot on a few titles you have the rights to mark. #### Price per hour of video The price is set per hour of video and depends on how many hours you send each month. - From $0.70 / €0.70 per hour of video. - A lower price per hour at higher monthly volume. - Contact us for volume pricing for a large library. #### How a pilot works - You send a few finished titles you have the rights to mark. - You tell us whether you need pre-rolls, mid-rolls, or both, and which markers: SCTE-35, HLS, or VMAP. - You receive the breaks with reasons and confidence, the markers, and the subtitles. - We explain how a full library would be pulled from S3, FTP, or HTTP and how results come back. #### How much does AdBreak cost? From $0.70 / €0.70 per hour of video. The rate depends on monthly volume, and the price per hour goes down as volume grows. Email hello@adbreak.dev for volume pricing. #### How do we start? With a pilot on a few titles you have the rights to mark. Email hello@adbreak.dev with the hours of video you expect each month and the markers you need. ### Choose how we get in touch. There are two ways to reach us. Leave a name and a phone number or email, and we contact you. Or fill in the detailed form with your organization, monthly hours of video, archive, and formats, and we reply with a demonstration and a price offer. Pricing starts at $0.70 / €0.70 per hour of video and goes down as monthly volume grows. #### Which form to choose - Contact me: when you want to talk first, or the volume is not clear yet. Two fields, and we take it from there. - Demo and price: when you know roughly how many hours a month you have. The demonstration and the price offer come in the first reply. - Not sure about the numbers? Pick “Not sure yet” in the detailed form, or start with the short one. #### What happens after you send a form - We read your request and prepare a demonstration: break times with reasons and confidence, SCTE-35 or HLS markers, and subtitles. - A price offer for your monthly volume arrives by email. The price per hour falls as volume grows. - If you want to see results on your own titles, we agree on a pilot and on how files reach us: S3, FTP, HTTP, or the HTTP API. ### Ways to find ad breaks, compared. Teams find ad breaks in four common ways: marking by hand, placing breaks on a fixed timer, building on generic shot and black-frame detection, or using an ad break feature inside one video platform. AdBreak is a separate service that reviews a finished file and returns ready break times with reasons and markers, without tying you to one platform. #### Side by side | Criterion | Manual marking | Fixed timer | Shot and black-frame detection | Feature inside a video platform | AdBreak | | --- | --- | --- | --- | --- | --- | | Keeps breaks off speech | Yes, if the editor checks | No | Not by itself | Depends on the platform | Yes, with the distance to speech | | Reason and confidence per break | In the editor’s head | No | Raw signals only | Depends on the platform | Yes | | SCTE-35, HLS, VMAP markers | Written by hand | Yes | Built by your team | Inside that platform | Yes | | Subtitles from the same review | No | No | No | Depends on the platform | SRT and WebVTT, 22 languages | | Scales to a large library | Slowly | Yes | With engineering work | Within that platform | Files processed as they arrive | | Tied to one platform | No | No | Often to one cloud | Yes | No | #### When AdBreak is the right choice - You own finished files and need break times, not a new video platform. - You need a reason for each break that ad operations can check. - You need SCTE-35, HLS, or VMAP markers delivered to the systems you already run. - You want subtitles from the same review. #### When something else fits better - You need live ad insertion into a stream. AdBreak does not insert ads. - You need HLS or DASH packaging. AdBreak does not prepare streams. - You need brand-safety certification. AdBreak describes the scene; it does not certify it. ### Questions about ad break detection. AdBreak finds where a finished video can take an ad and returns the time, the reason, the confidence, and a marker: SCTE-35, HLS, or VMAP. It writes SRT and WebVTT subtitles in the same review and translates them into 22 languages. It does not insert the ad, prepare the stream, or certify brand safety. #### What is ad break detection? Ad break detection finds the moments in a video where an ad can start without cutting through the story: a scene change, a dark frame, the end of a line, or a silence. AdBreak returns those moments as times and markers. #### Which file does AdBreak need? A finished video file you have the rights to mark. AdBreak reviews the file itself. It does not use the title, the genre, or a program guide to choose breaks. #### Does AdBreak mark opening and closing credits? Yes. Opening and closing credits are marked on their own. #### How do we start? Request a pilot: email hello@adbreak.dev with the kind of files you have, whether you need pre-rolls, mid-rolls, or both, and whether a large library should be processed as files arrive. #### How much does AdBreak cost? From $0.70 / €0.70 per hour of video. The rate depends on monthly volume: the more hours a month, the lower the price per hour. Contact us for volume pricing. #### Do you store our video files? No. Files are deleted after processing. Originals can be pulled from S3, FTP, or HTTP, and the results are uploaded back. #### Does AdBreak accept IMF packages? Yes. AdBreak reads IMF packages as well as MP4, MOV, and ProRes files. #### Is there an API? Yes. Files can be sent and results collected through the HTTP API. Originals can also be pulled from S3, FTP, or HTTP, and results uploaded back. #### Can we set our own break rules? Yes. A preset sets the rules for each program length: minimum confidence, time skipped at the start and the end, the shortest gap between breaks, and the minimum and maximum number of breaks. ### Ad break glossary. Short, plain definitions of the terms that come up when video is prepared for ads: where an ad can start, how that time is passed to players and ad servers, and the kinds of services that sell ads inside video. Each term also says how it relates to AdBreak. #### Breaks and placements - Ad break: A moment in a program where an ad can run. A good ad break sits where the story already pauses. - Ad insertion point: The exact time at which an ad can start. AdBreak reports the cut or the dark frame itself. - Pre-roll, mid-roll, post-roll: An ad before the program, inside it, or after it. AdBreak returns all three placements. - Ad break detection: Finding ad insertion points automatically from the picture, the speech, and the sound of a file. - Preset: A saved set of break rules for each program length: minimum confidence, time skipped at the start and the end, the gap between breaks, and how many breaks a title gets. #### Markers and formats - SCTE-35: An industry standard for signaling ad breaks in video. AdBreak writes SCTE-35 markers for the breaks it keeps. - HLS marker: A marker in an HLS playlist that tells the player or ad insertion where a break begins. AdBreak can deliver break times as HLS markers. - VMAP: Video Multiple Ad Playlist: an XML file that lists when pre-rolls, mid-rolls, and post-rolls play. AdBreak can deliver VMAP. - VAST: Video Ad Serving Template: the format an ad server uses to describe the ad itself. That is the ad server’s job, not AdBreak’s. - SRT and WebVTT: Two common subtitle file formats. AdBreak writes both from the speech in the file. - IMF: Interoperable Master Format: a standard package for delivering finished films and series, with a composition playlist and MXF files. AdBreak accepts IMF packages as originals. #### Ways to sell ads in video - FAST: Free ad-supported streaming television: linear channels on streaming services, paid for by ads. - AVOD: Advertising-based video on demand: a free or cheaper catalog paid for by ads. - BVOD: Broadcaster video on demand: a broadcaster’s catch-up and on-demand service. - SSAI: Server-side ad insertion: ads are stitched into the stream on the server. It needs break markers such as SCTE-35. AdBreak supplies the markers; it does not insert ads. #### Signals in the file - Scene change detection: Finding where the picture moves to a new scene. One of the signals AdBreak reads. - Black frame detection: Finding dark frames and fades to black, a classic sign of a natural break. - Distance to speech: How many seconds separate a cut from the nearest speech. AdBreak reports it for every break. - Confidence: The break score scaled from 0 to 1, so a person can see how strong a break is. - Lower-third: Text at the bottom of the frame that names a person or a role. AdBreak detects lower-thirds and marks their times. - Credits detection: Finding where opening and closing credits run. AdBreak marks them apart from the breaks. ### Privacy policy. This page explains what personal data AdBreak.dev collects when you visit the site or receive an email from us, why we collect it, how long we keep it, and who else can see it. It also explains what happens to video files sent for processing and how to ask us to stop or to delete your data. #### Who is responsible The controller for this site and for our outreach emails is AdBreak.dev, [TODO: legal name and registered address of the company]. For any privacy question, request, or objection, write to hello@adbreak.dev. #### What we collect on the website - Every page you open, sent by a small script on the page through this site’s own address to our own analytics server at v2tc.top: the address of the page, the date and time, and the order of pages within a visit. - Your IP address and the approximate country derived from it with the offline DB-IP Lite database. The IP address is not sent to a third party for this. - Your browser’s user agent, from which we read the device type, operating system, and browser. - Where you came from: the referring site and any UTM parameters in the link. - How long a page stayed visible, sent by the same script when you leave it. - Clicks on links to other sites, email and phone links, and file downloads. - Google Analytics on www.adbreak.dev, which sets its own cookies and sends usage data to Google. #### Email open and click tracking Our outreach emails to companies contain a small image and links that pass through our analytics server at v2tc.top. Each recipient has a random identifier, so the record is linked to your email address, name, and company as listed in our contact list. - When the image loads, we record the time, IP address, country, and email client or device. Some mail services load images through their own proxy, so the data may show the proxy rather than you. - When you click a link, we record the time, IP address, and page. The page address then carries your identifier once, so that visit is linked to the email; the script removes it from the address bar right away. - Turning off images in your email client stops open tracking. - Every outreach email has an unsubscribe link. You can also reply to the email or write to hello@adbreak.dev. #### Contact forms The contact page has two forms. The short one sends us your name and a phone number or email. The detailed one sends your first and last name, organization, phone number, work email, expected monthly volume, archive size, the formats you need, a time frame, and your comment, if any. We use them only to contact you, send a demonstration and a price offer, and discuss working together. The legal basis is steps taken at your request before entering into a contract, Art. 6(1)(b) GDPR. - The request is saved on our own server and sent to our inbox. It is not added to the outreach list and is not shared with anyone else. - Your IP address is not saved with the request; it is used briefly only to limit repeated submissions. - We keep the request for up to 12 months after our last exchange, unless we start working together. You can ask us to delete it at any time. #### Cookies and local storage | Name | Purpose | Lifetime | | --- | --- | --- | | ab_vid (local storage) | Anonymous visitor identifier for our own analytics, sent only to our analytics server | Until you clear the site data in your browser | | _ga, _ga_* | Google Analytics | Set by Google, up to 2 years | #### Purposes and legal basis We process this data on the basis of our legitimate interest under Art. 6(1)(f) GDPR: to understand how the site is used and to follow up on business outreach to companies. We do not sell personal data and do not use it for automated decisions. - Measuring visits, sources, and popular pages to improve the site. - Knowing whether an outreach email reached its recipient and whether they were interested. - Keeping the site secure. - Answering requests sent to us. #### How long we keep data - Page views, visits, email opens, and clicks: 13 months, then deleted automatically. - Contact list entries for outreach: until you object or ask for deletion, or until we no longer need them for outreach. - Google Analytics data: according to the retention setting in our Google Analytics account. #### Video files you send for processing AdBreak does not store customer files: they are deleted after processing. Originals can be pulled from S3, FTP, or HTTP, and results are uploaded back to the location you choose. #### Who receives the data - Our hosting provider, which runs the site, the analytics server, and the database where the data is stored. - Google, for Google Analytics. Google may process data in the United States under the EU-U.S. Data Privacy Framework. - DB-IP provides only a downloadable database. No data is sent to DB-IP. - Nobody else, unless the law requires it. #### Your rights and how to object Under GDPR you can ask what data we hold about you and receive a copy, have it corrected or deleted, restrict its use, and object to processing based on legitimate interest. Write to hello@adbreak.dev; we answer within one month. You can also complain to your data protection authority. - To stop email tracking, use the unsubscribe link, reply to the email, or turn off images in your email client. - To stop site analytics in your browser, open https://www.adbreak.dev/?ab_ignore=1 once; ?ab_ignore=0 turns it back on. Turning off JavaScript also stops it. - To have your data deleted, write to us with the email address you were contacted at. - Objecting costs nothing and does not need a reason. #### Changes to this policy Last updated: 2026-11-02. When the way we handle data changes, we update this page and the date above. ## Blog articles (English) ### SCTE-35, VMAP and VAST: what each one actually marks https://www.adbreak.dev/blog/scte-35-vs-vmap-vast-ad-break-markers (published 2026-11-20, English) SCTE-35 says where a break sits in a stream. VMAP lists where breaks sit in a piece of content, for a player to read. VAST describes the ad that plays inside a break. They are three layers, not three rivals: a finished video can carry SCTE-35 or HLS markers, a VMAP playlist, or both, and each break can still point to a VAST response. #### The short version | Name | Defined by | What it says | Where it travels | Who reads it | | --- | --- | --- | --- | --- | | SCTE-35 | SCTE (ANSI/SCTE 35, digital program insertion cueing messages) | A splice point: where a break starts or ends, often with a duration | Inside the stream, or translated into the manifest (MPEG-TS, HLS, DASH) | Packagers, server-side ad insertion and ad decision systems | | HLS markers (EXT-X-DATERANGE, EXT-X-CUE-OUT and EXT-X-CUE-IN) | Apple’s HLS specification (DATERANGE); CUE tags are a widely used packager convention | The same break, written into the HLS playlist | The HLS media playlist | HLS players and ad insertion servers | | VMAP | IAB Tech Lab | A playlist of breaks: when each one plays, what type it is, where its ads come from | A separate XML document the player requests | Client-side ad players and SDKs | | VAST | IAB Tech Lab | One ad response: creative files, tracking, click-through | XML returned by an ad server | Players and server-side ad insertion | #### SCTE-35: a signal about the stream SCTE-35 is a cueing message standard from SCTE. A message carries a command and a time. The common commands are splice_insert, which marks leaving the program and returning to it, and time_signal, which is paired with a segmentation descriptor that says what the time stands for, such as the start or end of a program, a chapter or a placement opportunity. In broadcast, the messages travel as their own data stream next to the video in an MPEG transport stream. For HLS and DASH they are translated into manifest tags or events. What they never carry is the ad. SCTE-35 tells a downstream system where a break is and, optionally, how long it lasts. What plays in that gap is decided somewhere else. A splice point only works if the stream can be cut there cleanly. For video that means a frame the decoder can start from, which is why break times for SCTE-35 are best placed on or snapped to a keyframe. #### HLS cue markers: the same break in a playlist Inside an HLS playlist a break appears either as an EXT-X-DATERANGE tag carrying SCTE35-OUT, SCTE35-IN or SCTE35-CMD attributes, which the HLS specification defines, or as the older EXT-X-CUE-OUT and EXT-X-CUE-IN tags that many packagers and ad insertion servers still use. Which one your setup expects depends on your packager or ad insertion vendor, so ask before you generate anything. The tag below is the CUE form, shown with a 60-second break. HLS playlist fragment (CUE form): ``` #EXTINF:6.000, segment_0123.ts #EXT-X-CUE-OUT:DURATION=60 #EXTINF:6.000, segment_0124.ts ... #EXT-X-CUE-IN #EXTINF:6.000, segment_0134.ts ``` #### VMAP: a playlist of breaks for a player VMAP is an XML document that tells a player where the breaks in a piece of content are. Each AdBreak has a timeOffset, which can be start, end, a time such as 00:12:30.000, a percentage or a position number, plus a breakType (linear, nonlinear or display) and an AdSource that carries or points to the ad response. Because VMAP lives outside the video, it suits players that request their own ads. It says nothing about the frames at the offset, so the time still has to be a good place to cut. VMAP with one mid-roll: ``` ``` #### VAST: the ad inside the break VAST, from the same IAB Tech Lab family, is what an ad server returns for one request: which creative files to play, which tracking URLs to call and where a click goes. It has no idea where in your programme the break is. That is why a VMAP AdBreak points at a VAST response, and why a server-side ad insertion system takes its break position from SCTE-35 or manifest markers and its ad from VAST. #### Which one does your video need? - Server-side ad insertion, FAST channel playout or a packager: ask which marker it ingests. It is usually SCTE-35 or HLS markers, and the vendor’s documentation names the exact form. - Your own player with client-side ads: a VMAP playlist is the usual way to hand the player the break positions, and many client-side ad SDKs accept it. - A mix of platforms: one set of break times can be written in all three forms, because each is just a different place to put the same times. Decide the times first and the format second. Choosing good break positions is the hard part; the formats are packaging. #### Where AdBreak fits AdBreak reads a finished video file and returns the break times with the kind of pause, a reason, a confidence between 0 and 1 and the distance to speech. The same times can leave as SCTE-35, an HLS cue or VMAP, and SCTE-35 points snap to a keyframe unless that is turned off. AdBreak does not insert the ad and does not prepare the stream: your ad server supplies the VAST response and your player or packager does the insertion. See how it works and the integrations page. #### Is VMAP a replacement for SCTE-35? No. They sit in different places. SCTE-35 signals a break inside a stream or its manifest, and VMAP is a separate XML playlist for a player. Some setups use one, some use both. #### Does SCTE-35 contain the ad? No. SCTE-35 only marks where a break starts or ends and may give its duration. The ad is chosen by an ad decision system and described by a VAST response. #### Can one set of break times produce SCTE-35, HLS markers and VMAP? Yes. All three describe the same moments in different places. The formats differ in what else they carry, such as duration, break type or the ad source. ### How to find ad-break points in archive content https://www.adbreak.dev/blog/find-ad-break-points-in-archive-content (published 2026-11-20, English) Work in two steps. First collect candidate pauses: shot changes, black frames, silence and the end of a phrase. Then apply rules that keep breaks apart, away from the start, the end and the credits, and clear of speech. A person accepts or rejects the shortlist. Tools such as ffmpeg find candidates; the rules and the review decide which become breaks. #### Start with what a good break is - It sits in a natural pause of the story, not in the middle of a sentence. - It keeps some distance from speech, so the cut does not clip a word. - It lands on a frame that a player or packager can cut cleanly, normally a keyframe. - It stays out of the opening and closing credits and away from the first and last moments of the programme. - It is far enough from the previous break, and the total fits the limits your ad operations or contract set. #### Step 1: collect candidates ffmpeg can list timestamps for the usual pause signals without editing the file. The thresholds below are starting points, not recommendations; tune them per title and genre. Black frames: look for black_start lines: ``` ffmpeg -i episode.mp4 -vf "blackdetect=d=0.1:pix_th=0.10" -an -f null - ``` Silence: look for silence_start lines: ``` ffmpeg -i episode.mp4 -af "silencedetect=noise=-35dB:d=0.5" -vn -f null - ``` Shot changes: look for pts_time values: ``` ffmpeg -i episode.mp4 -vf "select='gt(scene,0.4)',showinfo" -an -f null - ``` None of these signals is a break on its own. Many files have no fades to black, silence often happens under music or effects, and a shot change is just a cut. They produce candidates. #### Step 2: rank the candidates - A black frame together with a quiet stretch is stronger than either alone. - A shot change right after a speaker finishes is stronger than one in the middle of a conversation. - Speech timing matters most. Transcript or voice-activity timestamps give you the end of each phrase, so you can measure how far every candidate is from the nearest speech. - Keep the reason for each pick, such as “dark screen” or “end of a phrase”, so a reviewer can judge it quickly. #### Step 3: apply the rules | Rule | Why it exists | What you set | | --- | --- | --- | | Skip the start and the end | Keeps the opening and the close of the programme intact | Seconds ignored at each end | | Minimum gap between breaks | Stops breaks from clustering | Shortest allowed distance between two breaks | | Number of breaks by programme length | A feature film and a short episode need different amounts | Minimum and maximum breaks per length band | | Minimum confidence | Filters weak candidates before a person sees them | A score threshold | | Distance from speech | Avoids clipping dialogue | Shortest allowed gap to the nearest speech | | Credits | Opening and closing credits are not story pauses | Detect and exclude the credit range | There is no universal number for any of these. Take them from your ad operations policy and your platform’s rules, and test them on a few titles. #### Step 4: put the break on a cuttable frame For SCTE-35 and HLS markers the splice should fall on a keyframe or a segment boundary. Otherwise the packager has to cut late, or the player has to decode extra frames. This command lists video packets with a K flag for keyframes, so you can find the nearest one after each chosen time. Keyframe times (packets with the K flag): ``` ffprobe -v error -select_streams v:0 -show_entries packet=pts_time,flags -of csv=p=0 episode.mp4 | grep ",K" ``` #### Step 5: review and export Reviewing a shortlist of a dozen candidates is much faster than scrubbing a whole file, and a person keeps the last word on taste and context. Keep a record for every break: time, reason, confidence, distance to speech and whether it was accepted. That record lets you tune the rules later. Then write the accepted times in the form your downstream system ingests; this guide explains the options. #### Doing it for a whole library The method does not change at library scale, but consistency matters more. Use the same presets for programmes of the same length, process files as they arrive instead of in one big batch, and watch how often reviewers reject breaks, because that is the quickest signal that a rule is off. AdBreak runs steps 1 to 4 on a finished file. It reads scene changes, dark frames, speech, silence, loudness and motion, applies presets set by programme length (minimum confidence, time skipped at the start and the end, the shortest gap between breaks and the minimum and maximum number of breaks), detects opening and closing credits apart from the breaks, and returns each break with a time, a reason, a confidence and the distance to speech. See how it works, or estimate the effort with the cost calculator. #### Can I place ad breaks only on black frames? Rarely. Many files have no fades to black, so black frames alone leave gaps. Combine them with silence, shot changes and speech timing, then review. #### How close to speech can a break be? There is no universal rule. Set a minimum gap that fits your content and test it on a few titles. AdBreak reports the distance to speech for every break so you can filter on it. #### Do I still need a human in the loop? A short review is worth keeping. A person can accept a break or set it aside before the marker goes out, which also gives you data to tune the rules. ### Manual vs automated ad-break marking: how to work out the cost https://www.adbreak.dev/blog/manual-vs-automated-ad-break-marking-cost (published 2026-11-20, English) Manual cost is hours of video times minutes of work per hour, times a loaded hourly rate. Automation swaps most of that for a per-hour price plus a shorter human review. The only reliable inputs are your own, so time ten representative titles and compare. This guide gives both formulas, a worked example with stated assumptions and a free calculator. #### The manual cost formula Manual marking: ``` manual cost = hours of video × minutes per hour of video ÷ 60 × loaded hourly rate ``` - Hours of video: the running time you need marked, not the number of titles. - Minutes per hour of video: everything a person spends on it, including QC, rework and entering the markers into your system. - Loaded hourly rate: salary plus benefits and overhead, or the contractor rate. Use the cost to you, not the pay slip. #### Measure your own minutes Published figures for how long marking takes vary by content, tooling and standard, so treat any number you read, including ours, as a prompt to measure. Pick ten titles that represent your library, such as a few genres and lengths. For each one, time three things separately: the first pass, the QC pass and entering the markers. Divide by the running time of each title and look at the average and the spread. #### The automated cost formula Automated marking with review: ``` service cost = hours of video × price per hour review cost = hours of video × review minutes per hour ÷ 60 × loaded hourly rate total = service cost + review cost ``` Automation does not remove the person. A person can still accept a break or set it aside before the marker goes out, so the formula keeps a review term. AdBreak pricing starts from $0.70 / €0.70 per hour of video and falls as monthly volume grows. No tier breakpoints are published, so ask for a price for your volume. #### A worked example, with made-up inputs The inputs below are assumptions chosen to show the arithmetic. They are not benchmarks or customer results; replace every one of them with your own. | Line | Assumption | Result | | --- | --- | --- | | Manual marking | 30 minutes per hour of video, $40 per hour loaded | 500 × 30 ÷ 60 = 250 hours of work, $10,000 | | Automated service | $0.70 per hour of video | 500 × 0.70 = $350 | | Automated review | 10 minutes per hour of video, $40 per hour loaded | 500 × 10 ÷ 60 = 83.3 hours of work, $3,333 | | Automated total | Service plus review | $3,683 | | Difference | Manual minus automated | $6,317 in favour of automation under these assumptions | The break-even point is simple. Automation costs less when manual minutes per hour are greater than review minutes per hour plus price × 60 ÷ hourly rate. With these inputs that is 10 + 0.70 × 60 ÷ 40 = 11.05 minutes. If your people mark an hour of video faster than that, or review would take longer than marking, the formula says stay manual. #### What the formula leaves out - Turnaround. A backlog of hundreds of hours is not only a cost; it is calendar time during which the titles earn nothing from ads. - Consistency. Several editors rarely place breaks the same way. Presets make the rules explicit. - Delivery. Writing SCTE-35, HLS markers or VMAP by hand is another step; automation can produce them from the same times. - Setup. Connecting storage and agreeing formats takes some effort, so run a pilot first. - The value of a better or worse break. It is real but hard to measure, and this page does not put a number on it. Manual marking is still the right choice for a handful of titles, for one-off jobs where setup would cost more than it saves, and for premium content where an editor wants full creative control over each position. #### How to run a fair pilot 1. Choose five to ten titles that cover your genres and lengths. 2. Mark them the way you do today and record the time for each stage. 3. Run the same titles through the automated route and record the review time. 4. Compare accepted breaks, rejected breaks and total minutes, not only cost. 5. Put your own numbers into the calculator and decide. If you would like to try this on a few of your titles, request a demo and price. To see how breaks are chosen, read how to find ad-break points in archive content. #### How much does AdBreak cost? AdBreak starts from $0.70 / €0.70 per hour of video. The rate is lower at higher monthly volume, and no tier breakpoints are published. Ask for a price for your volume. #### Does automation remove human review? No. A person can accept a break or set it aside before the marker goes out. That is why the calculator and the formula include review minutes. #### What is a loaded hourly rate? The full cost to you of one hour of a person’s time: salary plus benefits and overhead, or the contractor’s rate. ## Free tools (English) - [Blog](https://www.adbreak.dev/blog): Practical guides on ad break markers, finding break points in archive video, and what manual marking costs. Written for FAST, library, broadcast and streaming teams. - [SCTE-35, VMAP and VAST: what each one actually marks](https://www.adbreak.dev/blog/scte-35-vs-vmap-vast-ad-break-markers): What SCTE-35, HLS cue markers, VMAP and VAST each mark, where they live, who reads them, and which one a finished video file needs. - [How to find ad-break points in archive content](https://www.adbreak.dev/blog/find-ad-break-points-in-archive-content): A practical method for placing mid-roll breaks in finished episodes and films: candidate signals, ranking, spacing rules, keyframes and ffmpeg commands to start with. - [Manual vs automated ad-break marking: how to work out the cost](https://www.adbreak.dev/blog/manual-vs-automated-ad-break-marking-cost): How to work out what it costs to mark ad breaks by hand versus with automation: the formulas, a worked example with stated assumptions, what to leave out, and how to run a fair pilot. - [Cost calculator](https://www.adbreak.dev/tools/ad-break-marking-cost-calculator): Free calculator: enter your hours of video, minutes per hour and hourly rate to compare manual ad-break marking with automated marking plus review. ## Contact Email hello@adbreak.dev with the kind of file, whether you need a pre-roll, a mid-roll, or both, and whether a large library should be processed as files arrive. ## Pages - [AdBreak home](https://www.adbreak.dev/en): AdBreak finds natural ad breaks in finished video and returns SCTE-35, HLS, or VMAP markers with the reason for each, plus subtitles in 22 languages. - [How it works](https://www.adbreak.dev/en/how-it-works): How AdBreak finds ad insertion points in a finished video: picture, speech, silence, and loudness, with a reason and confidence for every break. - [Integrations](https://www.adbreak.dev/en/integrations): AdBreak pulls originals from S3, FTP, HTTP, or its HTTP API, and returns SCTE-35, HLS, or VMAP markers and SRT and WebVTT subtitles the same way. - [Use cases](https://www.adbreak.dev/en/use-cases): Where ad break detection helps: FAST channels, AVOD back catalogs, broadcasters with BVOD and catch-up, and streaming platforms with mid-rolls. - [FAST channels](https://www.adbreak.dev/en/use-cases/fast-channels): Prepare FAST channel content with ad breaks: natural mid-roll points and SCTE-35 markers for episodes and films that arrive without them. - [Studios and libraries](https://www.adbreak.dev/en/use-cases/library-monetization): Turn an unmarked film and series library into AVOD-ready inventory: ad break times, SCTE-35 or VMAP markers, and subtitles for every title. - [Broadcasters](https://www.adbreak.dev/en/use-cases/broadcasters): Ad break markers for broadcasters: mark files before playout and prepare BVOD and catch-up with natural mid-rolls and SCTE-35 markers. - [Streaming and OTT](https://www.adbreak.dev/en/use-cases/streaming-platforms): Mid-roll placement for streaming and OTT platforms: natural ad breaks that keep dialogue whole, with VMAP or SCTE-35 markers for your ad server. - [Enterprise](https://www.adbreak.dev/en/enterprise): Ad break detection for large libraries: originals from S3, FTP, or HTTP, results uploaded back, an HTTP API, and files deleted after processing. - [Pricing](https://www.adbreak.dev/en/pricing): AdBreak pricing starts at $0.70 / €0.70 per hour of video. The rate depends on monthly volume, and the price per hour falls as volume grows. - [Contact](https://www.adbreak.dev/en/contact): Ask AdBreak to contact you with just a name and a phone or email, or request a demonstration and a price offer for your volume. - [Compare](https://www.adbreak.dev/en/compare): Manual marking, fixed timers, shot detection tools, and platform features compared with AdBreak for finding ad breaks in finished video. - [FAQ](https://www.adbreak.dev/en/faq): Answers about AdBreak: what ad break detection does, SCTE-35 and VMAP markers, subtitles in 22 languages, large libraries, and pilots. - [Glossary](https://www.adbreak.dev/en/glossary): Plain definitions of ad break terms: SCTE-35, HLS markers, VMAP, VAST, SSAI, FAST, AVOD, BVOD, IMF, lower-thirds, presets, and mid-rolls. - [Privacy](https://www.adbreak.dev/en/privacy): How AdBreak.dev handles personal data: site analytics, cookies, email open and click tracking, video files, retention, and your rights under GDPR. ## Other languages - Русский: [Главная](https://www.adbreak.dev/ru), [Как это работает](https://www.adbreak.dev/ru/how-it-works), [Интеграции](https://www.adbreak.dev/ru/integrations), [Сценарии](https://www.adbreak.dev/ru/use-cases), [FAST-каналы](https://www.adbreak.dev/ru/use-cases/fast-channels), [Студии и архивы](https://www.adbreak.dev/ru/use-cases/library-monetization), [Вещатели](https://www.adbreak.dev/ru/use-cases/broadcasters), [Стриминг и OTT](https://www.adbreak.dev/ru/use-cases/streaming-platforms), [Для крупных компаний](https://www.adbreak.dev/ru/enterprise), [Цены](https://www.adbreak.dev/ru/pricing), [Связаться](https://www.adbreak.dev/ru/contact), [Сравнение](https://www.adbreak.dev/ru/compare), [Вопросы](https://www.adbreak.dev/ru/faq), [Глоссарий](https://www.adbreak.dev/ru/glossary), [Конфиденциальность](https://www.adbreak.dev/ru/privacy) - Deutsch: [Start](https://www.adbreak.dev/de), [So funktioniert es](https://www.adbreak.dev/de/how-it-works), [Integrationen](https://www.adbreak.dev/de/integrations), [Anwendungsfälle](https://www.adbreak.dev/de/use-cases), [FAST-Kanäle](https://www.adbreak.dev/de/use-cases/fast-channels), [Studios und Archive](https://www.adbreak.dev/de/use-cases/library-monetization), [Sender](https://www.adbreak.dev/de/use-cases/broadcasters), [Streaming und OTT](https://www.adbreak.dev/de/use-cases/streaming-platforms), [Enterprise](https://www.adbreak.dev/de/enterprise), [Preise](https://www.adbreak.dev/de/pricing), [Kontakt](https://www.adbreak.dev/de/contact), [Vergleich](https://www.adbreak.dev/de/compare), [FAQ](https://www.adbreak.dev/de/faq), [Glossar](https://www.adbreak.dev/de/glossary), [Datenschutz](https://www.adbreak.dev/de/privacy) - Français: [Accueil](https://www.adbreak.dev/fr), [Fonctionnement](https://www.adbreak.dev/fr/how-it-works), [Intégrations](https://www.adbreak.dev/fr/integrations), [Cas d’usage](https://www.adbreak.dev/fr/use-cases), [Chaînes FAST](https://www.adbreak.dev/fr/use-cases/fast-channels), [Studios et catalogues](https://www.adbreak.dev/fr/use-cases/library-monetization), [Diffuseurs](https://www.adbreak.dev/fr/use-cases/broadcasters), [Streaming et OTT](https://www.adbreak.dev/fr/use-cases/streaming-platforms), [Entreprise](https://www.adbreak.dev/fr/enterprise), [Tarifs](https://www.adbreak.dev/fr/pricing), [Contact](https://www.adbreak.dev/fr/contact), [Comparatif](https://www.adbreak.dev/fr/compare), [FAQ](https://www.adbreak.dev/fr/faq), [Glossaire](https://www.adbreak.dev/fr/glossary), [Confidentialité](https://www.adbreak.dev/fr/privacy)