Why your meeting recording should be yours, as an MP4

Most platforms lock the recording inside their own player and put downloads on a higher tier. We did the opposite: every session's MP4 is free on every plan. Here is why.

Download arrow and MP4 label on a blue ribbon

When a session ends, the most valuable thing left behind is the recording. The person who could not attend watches it, the organizer reviews their own delivery, the organisation files it in its archive. Even so, many video conferencing products only show the recording in their own player; downloading the file costs extra or is not possible at all.

At Dasmeet we made this part of the foundation: the MP4 recording of every session is a free download on every plan.

What a player-locked recording costs you

BigBlueButton's default recording is not a single video file; presentation, audio, whiteboard strokes and chat are stored as separate layers and composed in the browser at playback time. It is a rich experience, but it has three practical problems:

  • You cannot move the recording to another system (LMS, video archive, sharing platform).
  • The day you leave the service, the recordings leave with it.
  • Playback struggles on mobile devices and weak connections.

What MP4 changes

MP4 is the common language every browser, every phone and every LMS can play today. Once you download it:

  • It goes into your own archive; retention and access rules are your decision.
  • You upload it to Moodle, Canvas or your corporate portal as a plain file.
  • You trim it, add subtitles; the file is yours.

How it works

When a session ends, BigBlueButton processes the recording; depending on the session length this takes minutes or hours. Once processing finishes, Dasmeet converts the recording to MP4 and makes it available in the panel. For organisations working through the API, the same file is listed as a format in the getRecordings response; your existing LMS plugin already shows it.

Why free

Making the recording a plan-dependent privilege means forcing an organisation to pay for access to its own data. We do not think that is right. The data belongs to the organisation; we run the infrastructure. We treat this as an assumption of the product, not a line in the price list.