Is Analysport compatible with Dartfish?

Analysport is built to prep exports that fit into existing video workflows, and Dartfish can be one of them. But we won't promise guaranteed compatibility without validating it against real files first.

Is Analysport compatible with XPS?

Same principle. Analysport can help you prep a usable base before an XPS workflow, but the formats have to be tested and validated on concrete cases before we claim full compatibility.

Why mention Dartfish and XPS if compatibility isn't guaranteed?

Because they're key tools in handball video workflows. Analysport positions itself upstream: pre-clipping, correction, annotation and export prep. Advanced compatibility has to be built with real-world testing.

Which export format matters most at the start?

A clean CSV is often the best starting point: readable, testable, controllable and simpler to validate with real users.

Do skipped clips show up in the export?

The goal is for skipped clips to stay out of the final export. The export has to respect the status the user defined.

Are timecode corrections preserved?

It's a core principle: if a user corrects the start or end of a sequence, the export has to reflect that correction.

Are annotations exported?

Depending on your plan and the available features, the goal is to keep the useful annotations: phase, outcome, player, comment or status.

Why does the export matter so much?

Because it's what the user actually walks away with at the end. If the export doesn't reflect the work corrected in Analysport, the product loses its value.

Dartfish and XPS handball video export

A useless export breaks the whole video workflow

Good clipping isn't enough.

If corrections aren't saved, if annotations vanish, if skipped clips show up anyway, or if the export doesn't reflect what you validated, the product loses its value.

For a coach or an analyst, the export is the moment of truth.

It's what you use next for your debrief, your staff feedback, your opponent scouting or your work inside an existing video tool.

Corrected clips that stay corrected
Annotations that get preserved
Skipped sequences that don't come back
Timecodes that reflect the final work
An export that's clear, clean and usable

An export shouldn't be a technical dump. It should mirror your real work.

The golden rule: visible, saved, exportable

Analysport follows one simple rule: every correction made in the tool must be visible, saved and exportable.

Adjust a clip, and that correction stays.

Add a note, and it's kept.

Skip a sequence, and it won't reappear in your final export.

The export isn't a side option. It's the product promise.

Analysport hands you an exportable base after correction

You upload your match, the AI prepares the clips, you correct and annotate, then you pull a cleaner base into your workflow.

Analysport shouldn't force you to rebuild your whole video setup.

The product helps you prepare a usable base faster: clips, timecodes, annotations, statuses and useful info depending on your plan.

You keep control over what comes out.

Clips generated from your match footage
Sequence corrections before export
Timecode adjustments
Action annotations
Statuses: validated, to review, skipped
Export a cleaner, more usable base

What you export should match what you actually validated.

How the export workflow works

The export comes after the real work: review, correct, annotate, select.

1
Upload the match
Add your video to Analysport straight from your browser.
2
Clip preparation
The AI prepares a first base of sequences so you don't start from raw footage.
3
Correction
You fine-tune starts and ends, correct the phases, skip the useless clips and keep the sequences that matter.
4
Annotation
You add the useful info: phase, outcome, team, player, comment or status.
5
Export
You pull a usable base for your debrief, your staff feedback or your existing video workflow.

Built for Dartfish, XPS and in-house club workflows

Plenty of coaches and analysts already work with tools like Dartfish, XPS or a video setup specific to their club.

Analysport shouldn't break those habits.

The product steps in upstream: it prepares a cleaner base of clips and data, then the Dartfish export, in a format compatible with XPS, lets you pick it back up in your existing workflow.

Every setup has its own settings. For the most specific cases, it's best to test the export on one of your real matches and check that it fits your workflow.

A good export isn't judged on the promise. It's judged on what it lets you pick back up in your real workflow.

See also the Dartfish workflow and the XPS workflow.

What the export needs to be able to carry

A useful export doesn't just list clips. It carries the info that lets you reuse the work.

Timecodes

Start, end and duration of each sequence must reflect the corrections made in Analysport.

Game phases

Set offense, fast break, 7-meter or any other classification that fits your model.

Outcomes

Goal, turnover, foul, goalkeeper save, 7-meter won or any other result useful for analysis.

Annotations

Comments, key player, team involved or notes added by the coach or analyst.

Statuses

A validated clip should come out. A skipped clip shouldn't. A clip to review should be handled however the user decides.

Match data

Team, opponent, match date or context to find and reuse the analysis later.

The export should produce a clean base, not a file full of noise.

A clean export, ready to use

The export carries your work exactly as you validated it, with no useless noise.

You get a base that's readable, controllable and usable straight away in your workflow.

Each sequence comes out with the info that matters to the coach or analyst: timecodes, annotations and statuses.

Each sequence clearly isolated
No useless technical info
Clear timecodes
Readable annotations
Usable statuses
Data ready to check

You get a clean export, not a file to clean up by hand.

The export used to be a fragile step. Now it has to become a reliable output.

Bad export workflow

Corrections aren't carried over
Skipped clips show up again
Annotations vanish
Timecodes don't match
The final file has to be cleaned by hand
The user loses trust in the tool

Analysport workflow

Corrections are saved
Skipped clips are excluded
Annotations stay attached to the clips
Timecodes reflect the final work
The file is readable and usable
The user keeps control over the output

A reliable export saves time. A bad one wastes it.

Who is the export essential for?

The more structured your video workflow, the more critical the export becomes.

Club coach

You want clean clips to prep a debrief, a video session or player feedback.

Video analyst

You want a clean, corrected and annotated base before you put it to work in your usual tool or setup.

Pro staff

You want corrections, statuses and annotations to stay usable across the whole staff.

Youth academy

You want clean teaching sequences to support every player's progress.

Also available for handball coaches, handball video analysts, handball clubs and handball youth academies.

The user decides what comes out

Not every auto-generated sequence deserves to be exported.

Some are useful. Some need correcting. Some should be skipped.

That's exactly why the export has to respect the user's final work.

Export the validated clips
Exclude the skipped clips
Include clips to review or not, as needed
Keep the useful annotations
Preserve timecode corrections
Never overwrite manual work with an AI prediction

The final export should follow the coach or analyst's decision, not the raw prediction.

What we'd rather tell you honestly

Video export is a sensitive topic.

Every tool has its own formats, constraints, columns, imports and habits.

The Dartfish export works — in a format also compatible with XPS — and your clips export to MP4.

For the most unusual cases, we'd rather you check it on one of your real matches than promise you universal compatibility.

Dartfish export works
Export format compatible with XPS
MP4 export of your clips
No promise of universal compatibility
Best to test it on a real match

We'd rather make a clear promise we keep than a universal one you can't verify.

Why the export is a product feature, not a technical detail

Plenty of tools think about the export last.

Analysport has to think about it from day one.

Because the whole workflow rides on that output: correction, annotation, selection, debrief, analysis, sharing, archiving.

If the export is bad, the rest of the product gets less useful.

The export structures the workflow
Corrections have to survive the interface
Annotations have to stay useful
Useless clips have to be excluded
The final file has to be understandable
The staff has to be able to trust the result

A video analysis tool is only worth what you can actually use at the end.

Discover the AI auto-clipping too.

Built around what coaches and analysts actually need

Analysport is developed with real footage and feedback from handball coaches, analysts and staffs.

The need is clear: users don't just want to generate clips.

They want to correct them, enrich them and pull out a usable final result.

Real match footage
Video analyst feedback
Need for clean exports
User corrections take priority
Gradual improvement with real files

The export is proven on real matches, not just validated in the code.

Discover Analysport, the handball video analysis software.

Test the export on a real match

The best way to check an export workflow is to start from real footage, correct some sequences, add annotations and look at what you can actually pull out.

Test on real footage
Clips generated automatically
Corrections possible
Annotations depending on your access
Export depending on your plan
Hands-on evaluation of the workflow

Analyse my first match free Discover Analysport

1 match free · No credit card

Frequently asked questions about Dartfish and XPS exports

A good export should mirror your real work.

Upload a match, correct the clips, add your annotations and check whether Analysport can produce a usable base for your video workflow.

Analyse my first match free See the other features