Export and share
An export turns a time range of recorded footage into an ordinary video file you can keep, send or hand to an insurer or the police. Aperture can export one camera, several cameras as a zip or as one combined video, or a timelapse, and it can create a link that lets someone without an account watch one clip and nothing else. This page explains each option, what it costs the server, and how share links behave.
Opening the export dialog
Section titled “Opening the export dialog”The export dialog, Export & download clips, opens from three places:
- Playback on a desktop: Manage under the timeline, then Download clip or Timelapse export (both open the same dialog).
- Playback on a phone: Export clip in the control row.
- Dashboard: Download on the Video Archiving card in the overview column.
From Playback, the camera you are watching is already selected and the range is the minute before the playhead. From the Dashboard, the first camera is selected and the range is the last minute.
Exporting a clip
Section titled “Exporting a clip”- Under Cameras, tick the cameras to export. Click a selected camera again to remove it.
- Set From and To, to the second. The Last buttons (30 sec, 1 min, 5 min, 15 min) set From that far before To.
- Choose the options described below.
- Click the export button. Its text sums up what you will get, for example “Export 1m 00s clip · instant copy”.
The export runs on the server. You can close the dialog; the job keeps going, and the finished clip appears under Recent clips the next time you open it. Exports run one at a time, so a second export waits as Queued… until the first is done. A job that was interrupted by a restart of Aperture starts again when Aperture comes back.
One export covers at most 4 hours. For a longer stretch, export it in parts. A camera with no footage in the range fails a single-camera export with “no footage for” and the camera name.
You can export any footage that still exists, including footage older than the 30 days Playback lets you scrub back to.
Options and what they cost
Section titled “Options and what they cost”| You choose | How the file is made | Cost on the server | Result |
|---|---|---|---|
| One camera, no burn-in, Realtime | The recorded segments are joined and cut without re-encoding (“instant copy”) | Seconds, almost no CPU | An MP4 with the camera’s original quality and codec (H.264 or H.265) |
| Burn in timestamp | Re-encoded to H.264 with the camera name at the top left and the date and time at the bottom left | CPU for the whole length of the clip | An H.264 MP4; audio, if included, as AAC |
| Timelapse (8×, 30×, 60× or 120×) | Re-encoded to H.264 and sped up | CPU for the whole length of the range | An H.264 MP4 without sound, the range’s length divided by the speed |
| Include audio off | Sound is left out | None | A silent MP4 |
| Several cameras | One clip per camera, each made as above | The cost of each clip | A .zip with one MP4 per camera |
| Several cameras with Combine into one multi-view | All cameras re-encoded into one grid video at 15 frames per second | The most CPU of all options | One H.264 MP4 without sound |
The dialog shows the length of a timelapse before you start: for example “1h 00m → ~2m 00s” at 30×. Timelapse always drops the sound, so Include audio is unavailable while a timelapse speed is chosen.
The burned-in date and time are those of the footage, in the server’s time zone.
Re-encoding is the expensive part. On a modest server, a long burn-in or timelapse export can take minutes and keeps the CPU busy while it runs. Exports run one at a time so that a large one does not starve recording; see Capacity.
Combining several cameras
Section titled “Combining several cameras”With two or more cameras ticked, Combine into one multi-view appears.
- Off: you get a .zip with one clip per camera. A camera with no footage in the range is skipped, and the export fails only if none of the cameras has footage.
- On: you get one video with the cameras side by side. It supports up to 4 cameras, has no sound, and ignores burn-in and timelapse (they are hidden while it is on). Camera names are not drawn on the picture.
| Cameras | Layout | Size |
|---|---|---|
| 2 | Side by side | 1920 × 540 |
| 3 | The first camera across the top, the other two below | 1920 × 1080 |
| 4 | Two by two | 1920 × 1080 |
Each camera is scaled to its cell without keeping its shape, so in the three-camera layout a 16:9 camera in the top row is stretched to twice its width. Put a wide or panoramic camera first if you use three. Every camera must have footage in the range, or the combined export fails.
Footage on network storage
Section titled “Footage on network storage”Footage stored on an SMB or SFTP destination is copied to the server first and then exported, so such exports take longer and briefly need local space for the copies. See Storage.
Recent clips
Section titled “Recent clips”Recent clips in the export dialog lists your latest exports, newest first. Each shows the camera, the time range and its state:
| State | Meaning |
|---|---|
| Queued… | Waiting for the export before it to finish. |
| Processing…, or a percentage for burn-in exports | Being made. |
| Ready and the file size | Done. Download and Share appear. After the size, the dialog says when the clip is deleted (“deleted in 5 hours”), or that it is kept for its share link and until when. |
| A red message | The export failed; the message is ffmpeg’s reason. |
Delete removes the export and its file at once. A share link to it stops working and shows as expired. Each person sees only their own exports.
Cleanup runs once an hour, so a clip can stay up to an hour past its deletion time. Exports are stored on the server under the data directory, in exports (by default /var/lib/aperture/data/exports), and count as Aperture’s own files in the storage figures.
Downloading
Section titled “Downloading”Download fetches the file into your browser, with progress shown in a small panel at the bottom of the screen (Downloading, then Saved), and then hands it to the browser to save. The whole file is held in the browser’s memory until it is saved, so a long export can fail on a phone with little memory; download long exports on a computer.
The file is named after the camera and the start of the range, for example Front_door_2026-11-14_21-30-00.mp4. A multi-camera zip is named aperture-clips_ plus the start time, and the clips inside it are named after their cameras.
Share links
Section titled “Share links”A share link lets someone watch one exported clip in a browser without an account. It gives access to that clip and nothing else.
- In Recent clips, click Share on a clip that is Ready.
- In Share clip, choose when the link expires: 1 hour, 24 hours (the default), 7 days or Never.
- Optionally turn on Require a password and enter one, and Limit number of views with a number.
- Click Create link, then copy the link with Copy link.
A link keeps its clip on the server for as long as the link works, past the usual 24 hours. When the expiry you choose outlasts the clip’s own deletion time, the dialog says so with the clip’s size: “Keeps this 48 MB clip on the NVR until the link expires”, or, for Never, “until you revoke the link”. The space comes out of recording storage.
The recipient opens a plain page with the clip’s name (the camera name and “clip”), a video player and “Shared securely via Aperture NVR”. If you set a password, they first see “This clip is password protected” and a View clip button. The page asks search engines not to index it. They can play the clip and, through their browser’s player, save it.
Managing links
Section titled “Managing links”Your links are listed under Shared links in the export dialog, working ones first. A working link shows a lock if it has a password, when it expires, how many times it was viewed and the size of the clip it keeps. Below the list, the dialog adds up what your working links keep on the server (“These links keep 1.2 GB of clips on the NVR…”).
Revoke link deletes a working link at once; anyone who opens it afterwards sees “This link is no longer available.”, the same message as for an expired link. A link that has used up its views shows “This link has reached its view limit.”
A link that no longer works stays in the list, marked Expired with the reason: when it ended, “view limit reached”, “revoked”, or “the clip is no longer on the NVR” (you deleted the export). Remove link clears it from the list. Once a clip is gone, the hourly cleanup also removes the links that pointed at it.
Every opening of the page counts as a view, including a reload by the same person, so leave some headroom when you limit views.
For administrators, Settings › Recording & Storage counts the clips that share links keep, for all users, as part of App & database, and says how much of it they take.
What to know before you share
Section titled “What to know before you share”- The link uses your public address. It is built from
APERTURE_PUBLIC_URL. Someone outside your network can open it only if that address is reachable from the internet, for example through a reverse proxy. See Configuration. - The password travels in the address. After the recipient enters it, it is part of the page address, so it can end up in their browser history and in your reverse proxy’s logs. Aperture’s own request log records only
/api/paths, without the query. Treat the password as a light barrier. - Disabling an account ends its links. When an administrator disables a user, every link that user created is revoked at once and shows as expired with “revoked”. See Users.
- It is logged. Starting and downloading an export, and creating, revoking and opening a link, are recorded in the activity log. See Security.
Footage is protected while it is exported
Section titled “Footage is protected while it is exported”Retention deletes old footage on a schedule, and an export of footage near the end of its retention could otherwise lose its source halfway through. To prevent that, every export takes a lease on its cameras’ time range when it starts. While a lease is held, retention skips the footage it covers. The lease is released when the export finishes or fails, and expires on its own after 2 hours, so a stuck export cannot hold footage indefinitely on a full disk. Leases are stored in the database, so they also hold across a restart. See Recording pipeline.
Scripts and extensions that read historical footage can take the same protection through the API: POST /api/v1/cameras/{id}/lease with fromTs, toTs (Unix milliseconds) and ttlSec (at most 7200), and DELETE /api/v1/cameras/{id}/lease/{leaseId} to release it. See API.
Troubleshooting
Section titled “Troubleshooting”- “no footage for … in the selected range”. The camera recorded nothing in that range: it records on motion only, was offline, or the footage has been removed by retention. Check the camera’s rail in Playback.
- Exports with a burned-in timestamp fail, others work. Burn-in draws its text with the font file
/usr/share/fonts/truetype/dejavu/DejaVuSans-Bold.ttf. Check that it exists; on Debian and Ubuntu it comes with thefonts-dejavu-corepackage. - The recipient sees “This link is no longer available.” The link was revoked or expired, or its clip was deleted. Shared links shows which, under Expired. Export the footage again and create a new link.
- The recipient cannot open the link at all.
APERTURE_PUBLIC_URLis a LAN address that their device cannot reach.
Who can export and share
Section titled “Who can export and share”Anyone who is signed in can export the cameras they may see and share their own clips. An administrator can also delete anyone’s exports and revoke anyone’s links, and can list another user’s links through the API with GET /api/v1/shares?user=<id>, or everyone’s with ?all=true; each item then names its creator in createdBy. API tokens need the media:write scope to create exports and share links, and media:read to list and download them; see Scopes.
Related: Playback, Storage, Reverse proxy, Security.