Meet
Recording a meeting
A recording is made on one participant's own device, in their own tab, and lands in their own Nemi files. What that means for everybody else in the call.
On this page
Open the More menu and press Record this meeting. Your browser paints the call exactly as you are seeing it, mixes the audio you are hearing, and encodes the result. When you stop, the file is uploaded into your own Nemi files, where it counts against your storage and can be shared or deleted like anything else.
Nothing is recorded on our side, and nothing can be. The audio and video in a Nemi call travel directly between the participants and never reach a server of ours, so the only recording that can exist is one somebody makes on their own machine.
You press record
Everybody in the call sees a red dot straight away.
Your tab does the work
The call is composited and encoded on your device, at 720p.
You stop
The file uploads to your files and tells you when it has landed.
What a recording actually contains#
- Your view of the call. Your layout, whoever you had pinned, and your connection, including any frames you dropped. There is no separate clean feed to fall back on.
- 720p, 24 frames a second. A deliberate cap. Recording a call is real work on top of already sending your camera to everybody, and a recording is watched at a fraction of the size it was made at.
- One file. MP4 where your browser can make one, otherwise WebM. Up to 4 GB, which is well over an hour of call.
- Not the whiteboard or the notes. Those are separate documents that survive on their own.
Where the file goes#
| Who pressed record | Where the file lands |
|---|---|
| A signed-in participant | Their own Nemi files, in the workspace they were signed into, counting against their storage. |
| A guest with no account | Nowhere on our side. Recording is not offered to guests at all. |
A file has to belong to an account, so the button is simply absent for guests.
Stopping the recorder starts the upload, which reports progress and tells you when the file has landed. Pressing Leave stops the recording and lets the upload finish rather than holding the call open for it, so stay on the page for a moment after a long recording.
The red dot, and being recorded#
While anybody is recording, everybody in the call sees a red dot with the recorder's name on it, and it goes out the moment their recording stops. It is an announcement made by that person's browser. We cannot verify it and we cannot enforce it, because we cannot see the call at all.
So a recording of a meeting you attended can exist, and it can exist without your agreement: it is made by another participant, not by us, and we hold the finished file the same way we hold any file that person uploads. If you would rather not be recorded, the moment to say so is in the meeting. This is stated in the same terms in the privacy policy.
When something goes wrong#
The recording is not in my files.
Check that the upload finished before the tab closed. If it did land, it is an ordinary file in the workspace you were signed into when you joined, so look in the workspace rather than only in the one you are viewing now.
The upload was refused.
Almost always storage. A long call is a large file. See Storage and usage and Storage and auto-extend.
The recording is choppy, or my fan was loud.
Compositing and encoding a call on top of sending your own camera is heavy. Close other tabs, switch background effects off, and let the person on the most capable machine be the one who records.
Deleting the meeting did not remove the recording.
Correct. The recording is a file in somebody's workspace, not part of the meeting, so it is deleted where it lives.
There is no record button.
Recording is still rolling out, and it follows the host's account. If the host does not have it switched on yet, nobody in that meeting has it.
Related
Still stuck? Email support@nemilab.com and tell us what you were trying to do.