How it works, step by step.
How to use Freally Capture, version 1.2.1: build a scene, record it, go live, and everything around them. Every section says which systems a feature works on when it is not all three.
Getting started
Freally Capture is a desktop studio for Windows, macOS and Linux. This manual describes version 1.2.1, the current release.
- Open Freally Capture. The first time, it asks you to accept its licence agreement; then a setup wizard checks your graphics card and processor and proposes an encoder, a canvas size and a bitrate, with the reason for each.
- The studio opens on the program preview with the Scenes, Sources, Mixer and Controls docks. There is no account and no sign-in.
- On macOS, allow Screen Recording — and Camera and Microphone if you use them — in System Settings → Privacy & Security, then reopen the app. On Linux with Wayland, the desktop's own dialog asks which screen or window to share.
- Add your first source (see Build a scene) and you are ready to record or go live.
Build a scene
A scene is a stack of sources composed on the graphics card. A source can be shared by several scenes.
- In the Sources dock, click Add Source and pick a type: Display, Window, Game, Webcam / Capture Card, Browser, Media, Image, Text, Color or Audio.
- Add a Display Capture: the program preview fills with your screen.
- Add a Webcam source, drag it to a corner of the canvas and resize it with its handles.
- Add an Image or Browser overlay on top. The order of the list is the order on the canvas: the top of the list is the front.
- Create more scenes in the Scenes dock — for example "Starting Soon", "Gameplay" and "Be Right Back" — and switch between them.
Tip: Change a shared source's properties once and it changes in every scene that uses it.
The preview: on Windows, macOS and Linux with X11, the program preview is painted straight from the graphics card, so dragging, scaling and rotating feel instant. On Wayland a standard preview is used, with the same on-canvas editing.
Filters and transitions
Stack filters on each source, on the graphics card, and choose how one scene gives way to the next.
Add a chroma key
- Right-click a source — a green-screen camera, say — and choose Filters.
- Add Chroma Key and adjust the key color, similarity, smoothness and spill: the keyed color disappears live on the canvas.
- Add more filters as you need them — Color Correction, LUT, Blur, Mask, Sharpen — and drag them to reorder the chain.
Set a transition
- In Controls, open the transition picker, choose Cut, Fade, Slide, Swipe, Stinger or Luma Wipe, and set a duration.
- For a Stinger, pick the media and its transition point; for a Luma Wipe, pick the gradient and its softness.
- Switch scenes to see the transition play. In Studio Mode it plays when you send the preview to the program.
Compositor and visual effects
3D tilt, downstream keyers, freeze and clone, a family of blurs, motion transitions with rules, a shader studio, bezier masks and track-matte stingers.
3D tilt and perspective
- Open Edit Transform on an item and set Tilt X, Tilt Y and a Perspective strength to pin the source in 3D. A transform with no tilt renders exactly as before.
Downstream keyers
- Open Tools → Downstream Keyers and add any source as a layer over the program output, above every scene and through every scene change — a station logo, a LIVE badge, a lower third.
- Reorder the layers and set each one's opacity, position, size and on or off. They appear in the preview, the recording, the stream and the multiview alike.
Freeze-frame and source cloning
- Right-click a source, open Filters and add Freeze: it holds the last frame in the program, the preview, the recording and the stream together. Switch it off to unfreeze.
- Click the Clone button (⧉) on a source's row to place one feed in several scenes or spots, each clone with its own transform and filters.
Blurs
- In a source's Filters, add one of the blurs beside the Gaussian: directional (a motion streak at an angle), radial (a spin around a center), zoom (a dolly-zoom streak) or pixelate (a mosaic).
The move transition and transition rules
- Choose the Move transition: items in both scenes glide from their old position, scale, rotation and crop to the new ones instead of cutting, and items in only one scene fade in or out.
- Open Tools → Transition Rules to give one pair of scenes its own transition and duration. For an item's own entrance, set a Reveal fade-in under Edit Transform.
The WGSL shader studio
- Add a user WGSL effect as a filter and edit it live. Its sliders are made from
// @paramannotations, and a built-in gallery has grayscale, invert, scanlines and vignette.
Tip: A shader is compiled and checked as you type. An invalid shader is ignored and the source renders unfiltered — never a crash.
Bezier masks
- Add the freehand mask filter and draw a closed path: drag the handles, double-click to add a point, right-click to remove one. It has preset shapes, a feather for each edge, and invert.
- Export any path as a grayscale luma-wipe pattern to reuse the shape as a transition.
Track-matte stingers
- Set a stinger to carry its transparency as a track matte, with the fill and the matte side by side or stacked, so transparency survives codecs that drop it (H.264 and HEVC). Optionally duck the program audio under the stinger's own sound while it plays.
Overlays and more sources
Replay, playlists, titles, meters, a stats overlay, timers, an input overlay and two network feeds, all from the Sources dock's + / Add Source menu.
Instant replay
- Arm the replay buffer first (Arm Replay in the Controls dock), then choose Instant Replay from + / Add Source and place it in a scene.
- Roll the last seconds into the program with your replay hotkey — copied without re-encoding and played at 100%, 50% or 25% speed, slowed down rather than with invented frames. Scrub or pause while it plays.
- At the end the source clears itself, so the show returns to live on its own.
Tip: Slow-motion replay is silent on purpose: slowed-down audio would smear, so it is left out rather than faked.
Media playlist and background music
- Add Media Playlist (gapless) and build an ordered list with in and out points and cue points for each item. The whole list plays through one decoder, so the joins are frame-exact and truly gapless.
- Choose how it runs — loop, shuffle or hold last — and step through it with the next and previous hotkeys. An audio-only playlist shows the current track's name on the canvas and plays through its own mixer strip; click that strip's Monitor button to hear it.
- For music that plays without anything on screen, choose + / Add Source → Background Music… instead and pick one or more
.mp3,.wavor.flacfiles, shuffled if you like. It mutes a video backdrop's own sound, so only one thing is ever heard.
The title and scoreboard designer
- Add Title / Scoreboard to open the designer: stack text, image and shape layers, with outlined and shadowed text and animations in and out (fade, slide, wipe).
- Bind fields to a watched file (a CSV cell or a JSON pointer) or to a studio variable, then control it live: change a name, edit the score or play the animation without touching the scene.
The audio visualizer
- Add Audio Visualizer and pick a style — spectrum bars, an oscilloscope or stereo VU meters — then bind it to any mixer strip, track or the master mix. It shows a backdrop video's sound too.
- In the source's Properties, switch on Classic colors for the green, yellow and red bands, or leave it off for one solid color. Size, bar count and fall rate are there too.
Tip: The visualizer listens after the fader, so a muted source shows flat: it shows exactly what you hear.
The stats overlay, split timer and input overlay
- Add Performance Stats (HUD) to show the stats dock's measured numbers on the canvas — frames per second, CPU, memory, GPU compose time, dropped frames and live bitrate — each line on or off. GPU utilization is left out on purpose, because it is not measured.
- Add Speedrun Split Timer, import a LiveSplit
.lssfile, and run it with global split, undo, skip and reset hotkeys against your personal best, best segments or average. The file is only read; a run is never written back. - Add Input Overlay (keys/pad) to show the keyboard, mouse and gamepad live, in one of four layouts (WASD, a compact keyboard, a twin-stick pad, an 8-way fight stick). Keyboard and mouse work on Windows; gamepads work on all three systems.
The social and channels bar
- Add Social Bar from + / Add Source: a panel listing your handles. Pick a platform for each row — YouTube, Twitch, Kick, X, Instagram, TikTok, Facebook, Discord as colored badges, or Custom with your own label and color — and type the handle (for example
@mychannel). Add an optional header line ("Follow me"), reorder the rows, and set the text size and colors. - Every field stays editable in the source's Properties. Rows with no handle are skipped, so you can keep a full list and fill in only what you use.
The featured chat message
- Open Tools → Featured Chat Message… (or the command palette). It lists the newest lines from every running chat overlay: click Feature on one to pin it to the program as a banner that viewers of the stream and the recording see.
- Set the banner and text colors in the dialog, and click Clear to take it off air. The pin itself clears on restart, by design: yesterday's shout-out never haunts today's show.
Cursor highlight and click effects
- Right-click a Display or Window capture, open Filters and add Cursor effects: a cursor halo (color and radius), color-coded left and right click ripples, and optional keystroke ghosting beside the pointer. Changes show live.
Note: Cursor effects work on Windows only; macOS and Linux draw the cursor themselves. The input overlay and keystroke ghosting read input only while they are on, and draw it straight into the picture: nothing is stored or logged.
Network sources: LAN ingest and Freally Link
- Add LAN Ingest (SRT/RTMP listener) to open a listener on this computer, then point a phone camera app, an encoder or a second computer at the address shown (with a QR code). It lands in the scene with its own mixer strip. SRT can carry an optional AES passphrase; RTMP has no authentication of its own, so the form prefers SRT.
- To share between two copies of Freally Capture, turn on the Freally Link output on the sending computer and set its pairing key — it cannot be turned on without one. On the receiving computer, add Freally Link (another instance), click Scan the LAN and type the key: the sender's program appears as a source. Neither side needs ffmpeg, and a receiver without the key never sees a frame.
Note: Both network sources are off until you add them, stay on your own network, and never touch the internet: nothing finds you, and nothing dials out.
The Starting Soon countdown
A pre-show holding screen in one click: a big countdown to showtime over an image, a GIF, a video, a gradient or music, which flashes at zero and waits for you to cut to the show.
Add the countdown
- In the Sources dock, open + / Add Source and choose Starting Soon…. It places a full-canvas countdown — a caption above a big number — on the scene.
- Type the caption ("Starting Soon", "Be Right Back"), then set the time with the clock picker: an hour (1–12), a minute in five-minute steps, and AM or PM. The source counts down to that time of day.
- At zero the countdown flashes and holds at 0:00:00 — it never switches scenes by itself. Cut to your live scene when you are ready. Every field stays editable in the source's Properties.
Choose a backdrop
- Pick the fill: a two-color Gradient (the default), a Solid color, an Image (click Browse…), or Transparent to let a source underneath show through.
- Choose a GIF or a video file and it loops behind the numbers, scaled to fit and centered, so the whole picture shows and nothing is cropped.
- Add background music from the dialog's Browse… (MP3, WAV, FLAC, M4A, AAC, OGG or Opus). It loops, you hear it in the preview, and it is part of the recording and the stream. A video backdrop's own sound is muted, so only one thing is ever heard.
Tip: For music behind a plain screen, leave the backdrop on Gradient or Transparent and add the music: a clean countdown with a soundtrack.
The audio mixer
Mix every audio source, send it to up to 6 tracks, and clean up your microphone — all live.
- Each audio source is a strip in the Mixer: its name, a level meter, a fader, mute, monitor, filters and track dots (1–6).
- Drag a fader to set the level, click mute or monitor, and send the source to any of the 6 tracks.
- Open a source's filters and add Denoise (classic signal processing, no AI), Noise Gate, Compressor, Limiter, EQ or Gain.
- Bind a push-to-talk or push-to-mute hotkey, and watch the LUFS meter for the program's loudness.
macOS note: macOS does not give apps "what you hear" by itself. Use ScreenCaptureKit audio (macOS 13 or later) where it is available, or install a virtual device such as BlackHole and choose it as your system-audio source. Freally Capture guides you, and keeps recording even if one source cannot open.
Record
Record the program on several tracks with your graphics card's hardware encoder, or losslessly in Capture's own format.
- In Settings → Output, pick an encoder. Freally Capture finds NVENC, Quick Sync, AMF, VAAPI or VideoToolbox and chooses the best; x264 on the processor is always there as a fallback.
- Choose a container — MP4, MKV, MOV or WebM — or Capture's own lossless freally-video format (
.frec), which needs nothing else installed. - Send sources to audio tracks (up to 6) so the microphone, the system sound and your guests stay separate for editing. Optionally turn on file splitting and a separate-track local copy while streaming.
- Click Start Recording in Controls. A green REC dot shows the time and the number of tracks. Click Stop to finish the file.
Codec note: MP4 with H.264 and AAC (and HEVC or AV1) uses codecs covered by patents, provided by ffmpeg, which is not bundled: Freally Capture downloads it the first time you need it and checks it. The lossless freally-video format needs nothing downloaded.
Recording and replay depth
Everything around the file: separate recordings of each source, a clip trimmer, real transparency, splitting and markers on events, tasks after recording, an integrity check and SMPTE timecode. All of it is off until you turn it on, and none of it goes online.
Per-source ISO recording
- Open Settings → Output and find ISO recording. Turn on Record "{name}" as its own ISO file for each source you want clean: each is recorded before compositing, at the canvas size and frame rate, so every file lines up with the program on an editing timeline. Each remote guest is a source, so each guest gets a file too.
- Leave Record with the source's filters checked for the processed look, or uncheck it for the raw source, and pick each recording's ISO format and ISO video encoder. Audio is taken after the filters but before the fader and mute, so a mixing decision never silences an ISO file.
Tip: Two ISO recordings are comfortable on a mid-range graphics card; each one more costs another render and encode, and the panel says so.
The replay and clip trimmer
- Open a saved recording in the Trim window from the recordings list, step through it with Back one frame and Forward one frame, and set your points with Set in and Set out while you watch.
- Check the badge before you export. A green "Exports without re-encoding" means the in point sits on a keyframe (near-instant and lossless); the amber badge warns that it will re-encode — press Keyframe to snap the in point for a lossless cut. Click Export clip, or 9:16 to export a vertical version.
Recording with transparency
- In Settings → Output, turn on Record with transparency (alpha) to record the program over a transparent background to Capture's
.frecformat. The recording gets its own transparent render, so your preview and stream keep the normal picture. From the recordings list, export a ProRes 4444 or QuickTime Animation (QTRLE).movfor your editor; MP4 and MKV flatten the transparency.
Note: Transparency is only a flag in the
.frecheader, so these files play everywhere.frecdoes, and older files open as opaque.
Splitting and automatic markers
- In the split settings for
.frec, choose to start a new file on a scene switch, a marker or a rundown step. Each part starts on that event's exact frame, and a part lasts at least one second, so a burst of events cannot make a pile of tiny files. - Turn on Drop chapter markers automatically on studio events to mark scene switches, saved replays, reconnects, bursts of dropped frames, alarms and rule actions as chapters. They go into MKV chapter titles and the
.chapters.txtfile beside the recording, next to the markers you place with your hotkey.
After recording: the pipeline and the integrity check
- Build a Post-record pipeline for each profile from a fixed set of steps — Verify, Remux to MP4, Normalize loudness, Rename, Move to folder, Copy to folder, Reveal in file manager and Notify Lua scripts. It runs in the background with a live queue and stops at the first failure. There is deliberately no "run any command" step.
- Run the integrity check after a recording or whenever you like, for a plain OK, warning or fail on the container, video continuity, audio continuity, audio and video interleaving and duration.
.frecfiles get the deep check; other files get a structure and decode check through ffmpeg.
Export a shareable copy when you stop
- In Settings → Output, with the container set to
.frec, tick Also save a shareable MP4 next to the master. When a recording finishes, a background export writes an.mp4anyone can play beside the lossless master. - The copy appears in the post-record queue, is named so it never overwrites anything, and never touches the master. It is off until you turn it on.
SMPTE LTC timecode
- Open SMPTE Timecode (LTC), turn on Generate LTC onto a track, and pick the mixer track and frame rate to feed external recorders and cameras. Set Read LTC from to an audio input to show a timecode line on the stats overlay and to stamp LTC chapter markers. Classic audio timecode, fully offline, accurate to one frame at 24, 25 and 30 fps.
Go live
Stream straight from your computer to a platform over RTMP or RTMPS — never through a server of ours.
- Open Settings → Stream and click Add target. Pick Twitch, YouTube, Kick, Facebook, Trovo or Custom RTMP.
- Paste your stream key — kept on your computer and shown masked — and set the bitrate and encoder for that service.
- Click Go Live in Controls. The LIVE light comes on, and the stats dock shows your bitrate, dropped frames and the stream's health.
- If your connection drops, Freally Capture reconnects by itself, and your local recording keeps running whatever the stream does. Set a stream delay if you want one.
- Click End Stream to stop.
Broadcast safety
Not losing the show — before, during and after.
Before: the go-live pre-flight
Clicking Go Live first runs a checklist: stream targets have keys, a usable encoder is found, every source is healthy and there is enough disk space for the recording — each green or red, with a one-click fix — plus reminders about microphone and desktop-audio levels and the replay buffer, which never block a screen-only show. A setting can hold Go Live until every blocking check is green; otherwise "Go Live anyway" is there.
During: alarms, health and failover
- Safety alarms watch while you are live or recording: silent program audio, sustained clipping, a black or frozen picture, and a low-disk forecast ("about 22 minutes left at the current bitrate"). They appear as a banner you can dismiss, and screen readers announce them — never a dialog that interrupts the show.
- The source health dashboard (command palette → "Source health…") lists every source's state, frame rate, the age of its last frame, dropped frames and restarts, with Restart and Properties for each.
- If the hardware encoder fails in the middle of a stream or recording — a driver reset, the graphics card under strain — encoder failover switches to another hardware encoder or to x264. The stream reconnects and stays up, the recording continues in a new file, and a message says exactly what happened. Network problems never cause a switch.
- The panic button (a global hotkey you choose) cuts the program — and the vertical canvas and any projectors — to a privacy slate, stops every capture and mutes all audio, the microphone included, while the stream and recording stay connected. Coming back takes a deliberate two-step confirmation. Set the slate's color or image beside the hotkey in Settings → Hotkeys.
After: safe recordings and an orderly quit
- MP4 and MOV recordings are written in fragments, so a crash or a power cut still leaves a playable file (MKV and
.frecalready were). If a session ends in the middle of a recording, the next launch offers a one-click repair into a(repaired)copy; the original is never touched. - Quitting while live, recording or with replay armed shows what will happen, then shuts down in order: end the stream, finish the recording, save the replay buffer, save your work.
- Recording file names follow a template (Settings → Output) built from tokens —
{prefix}{date}{time}{scene}{profile}{canvas}{marker-count}{counter}— for recordings, replays and stills, with their own folders for replays and stills. - Export diagnostics saves a bundle of technical details to a file on your computer, built from a strict allowlist so that stream keys, passwords, file paths and names are never in it. You can read what it holds first; it stays where you save it and is never sent anywhere.
Sources and devices
Everything between the glass and the canvas: test signals, sync calibration, text from a file, timers, the hotkey map, mixer depth and real device controls.
Test signals and A/V sync calibration
- Add a Test Signal source (Sources → + → Test Signal): color bars, a calibration grid, a motion sweep, a 1 kHz lineup tone at −20 dBFS, or a combined flash and beep for audio-video sync — picture and sound made from one clock. Check a projector, an encoder or a stream target with no camera plugged in.
- Open the A/V sync calibration workbench (command palette → "A/V sync calibration…"). Pick the camera and microphone to line up, point the camera at the flashing program (the dialog can open a fullscreen projector for it), and let it measure for about twelve seconds. It finds the flash and the beep over several cycles and offers to apply the measured offset to the microphone; the manual slider stays as a fallback. The measurement runs through your screen and speakers, so their own small delays are part of it — and a failure says why.
Timers, clocks and text from a file
- A Timer source shows a clock (with your own format and an optional fixed UTC offset), a countdown (for a length of time, or to the next time of day — at zero it can flash or switch scene), a stopwatch, or the time since you went live or started recording. Start, pause and reset it from its Properties, or bind the two global hotkeys that drive every timer at once (Settings → Hotkeys).
- A Text source can read from a watched file (Properties → Read from file): a whole
.txtfile, one CSV cell (by column name or number), or one JSON value (a pointer such as/teams/0/score). Changes show within half a second. Scoreboards and lower thirds with no service behind them.
The hotkey map and the mixer console
- The hotkey map (command palette → "Hotkey map…") lists every binding — global actions and each source's push-to-talk and push-to-mute — searchable and filterable, and flags conflicts honestly: the same shortcut written two ways is shown as shared, and a key the system refused (because another app owns it) says so. Export cheat sheet writes a Markdown reference into your Downloads folder.
- Every mixer strip has pan (stereo balance; centered is exactly no pan, and a double-click resets it), PFL solo (the monitor hears only the soloed strips; the program mix never changes) and a mono fold-down. Pan and mono are in the strip's "⋯" menu; solo is on the strip itself.
Device depth: deinterlacing and camera controls
- A video capture device's Properties offer deinterlacing for interlaced feeds, such as capture cards fed by older cameras and consoles: discard, bob, linear, blend or motion-adaptive, with the field order. It runs the same on every system; changing it restarts the device.
- Camera controls — exposure, white balance, focus, zoom, gain and more — appear in the same Properties while the camera runs. Windows and Linux use the standard UVC controls; macOS shows whatever the system reports, which is often nothing, and the panel says so rather than showing sliders that do nothing. Every adjustment is saved in a profile for that camera, applied again when it is plugged back in or the app restarts; Reset profile returns the defaults.
Automation and control
Let the studio drive itself with rules, macros and hardware controllers — every one of them limited to one fixed list of studio commands, so no automation can name a file, start a program or reach the internet.
Rules, macros and variables
- Open Tools → Automation Rules & Macros… and add a rule. Pick one of nine triggers (a scene switch, the stream starting or stopping, the recording starting or stopping, a source error, an audio level crossing a line, the system going idle, a window taking focus, a time of day, or a watched file changing), add conditions (a variable's value, live, recording), and choose a studio action. Every rule starts disabled: turn it on to arm it.
- Build a macro as a named list of steps — run an action, wait, set a variable — with a repeat count and an optional global hotkey. Run it from the app, a hotkey, a rule or the remote-control API.
- Set a studio variable in a macro and use it as
{{name}}inside any Text source: the text changes the moment the macro sets the value.
Controllers: MIDI, OSC and the touch panel
- Open Tools → MIDI Control… and teach it a pad, knob or fader for an action, a macro, a scene switch, a mixer fader or a mute — with lights and motorized faders that follow the studio's real state. No MIDI port opens until you pick one.
- Turn on Listen for OSC to let TouchOSC-style controllers and lighting desks send addresses such as
/scene/switch,/record/start,/macro/runand/mixer/vol. It is off by default and listens only on this computer unless you allow your network. OSC has no password of its own. - Open Tools → LAN Panel & Tally… to serve a control page — scene buttons with live tally, mixer faders and action keys — to any phone through a QR code. Every request needs the password, and it listens only on this computer unless you allow your network. The tally page shows full-screen red or green; add
?scene=NAMEto watch one scene.
Hotkey chords and layers
- In a hotkey field, bind a plain shortcut (Ctrl+Shift+M) or a two-step chord (Ctrl+K, then 3) — the second key is claimed only while the chord is waiting. Give a binding a Layer so it works only while that layer is active; layers stay switched until you change them.
Cameras and the show rundown
- Open Tools → PTZ Cameras…, add a camera by its VISCA-over-IP address, store named pan, tilt and zoom presets, and link a preset to a scene so going to that scene recalls the shot. PTZ stays on your network, and a camera exists only because you typed its address: nothing is searched for.
- Open Tools → Show Rundown… and list the steps — a scene, how long it holds, and optional actions — advancing by hand or automatically, with a live "next up" and the time remaining. A rundown switches scenes the ordinary, undoable way and never edits your scene collection.
Note: Every rule, macro, MIDI or OSC binding, panel button and rundown step goes through the same fixed list of commands as the remote-control API, so no controller can do what the app's own buttons cannot. Every network listener is off by default and stays on this computer unless you allow your network, and the OSC and panel settings warn you that network traffic is unencrypted before the port opens.
Multistream
Stream to several platforms at once — straight from your computer, with no relay service in between.
- Add two or more stream targets in Settings → Stream and turn each one on.
- Give a platform its own encoder settings if it needs a different bitrate.
- Click Go Live: you broadcast to every target that is on, at once. The stats dock shows each target's health and bitrate, and one target failing never takes down the others.
- Optionally record a separate-track local copy at the same time, and save replays with the replay hotkey while you stream.
Free today: every feature — multistream, SRT and WHIP, every filter, scripting, replay, the transition packs and the remote-control API — is free today, for everyone. Future versions may be sold.
Streaming reliability and insight
Rehearse, measure and explain your show. Everything here is off or neutral by default, and none of it goes online.
The network simulator
- In Settings → Stream, open the Network simulator (rehearsals) and choose a Profile — Hotel Wi-Fi, Mobile hotspot, or Custom with your own Bandwidth, Latency, Jitter and scheduled Outage times. It affects only a rehearsal's local output, so you can practise reconnects, multistream and bitrate choices; it can never slow down a real broadcast.
Rehearsal mode
- Press the violet Rehearse button to run the whole pipeline — compositor, encoder, muxer and the real reconnect logic — into a local stand-in with nothing leaving the computer. A REHEARSAL badge marks every live control, and your stream keys are never even read, so you can rehearse before you have them. You can also record the rehearsal.
Tip: Pair a rehearsal with the network simulator to practise reconnecting over a weak, unsteady connection well before the day.
The dropped-frame timeline
- The Session timeline records the whole session — render time, encoder queue, each target's bitrate and dropped frames, reconnects, scene switches, markers and alarms — on one zoomable graph. Where the stats dock shows now, the timeline answers "what happened at minute 43?" afterwards.
The session report and the encoder benchmark
- Turn on Write a session report (HTML + Markdown) next to the recording in Settings → Stream for a local summary when the session ends: uptime, average and peak bitrate per target, the time spent down, the reconnects, markers, alarms and the recording's location. It stays on your computer and is off by default.
- Use Run encoder benchmark… to measure short encodes with every encoder, preset and resolution your computer has — about a minute, fully offline — then Apply to recording settings from the result. Failures are listed, not hidden, and the benchmark refuses to run while you are live or recording.
Sources only on the stream, or only in the recording
- On a source's row, use Show on stream / Hide on stream and Show in recording / Hide in recording to keep alerts and chat on the live stream while the recording stays clean, from one canvas. The main eye button still controls everything, and the preview, projectors and multiview always show the whole program.
Virtual camera
Use your program as a webcam in any video-call app. Windows only in 1.2.1.
- Click Start Virtual Camera in Controls. Freally Capture adds a system camera called "Freally Capture Virtual Camera".
- In Zoom, Meet, Discord or Teams, choose that camera in the video settings: your program becomes the webcam.
- Click Stop Virtual Camera to remove it.
Per system: on Windows the camera registers for your user, with no administrator rights, and is removed when you stop it. It is not yet code-signed, so Windows may warn about it and a hardened video-call app may refuse it; a full test inside a live call is still to be done. The macOS and Linux cameras are separate components that are not in this release. Freally Capture never installs a system component without asking, on any system.
Browser source
Put a live web page — an alert overlay, a scoreboard, a chat widget — straight into a scene.
- In Sources, click + and choose Browser.
- Paste an http:// or https:// address and set the size and frame rate to render it at.
- The first time, Freally Capture offers to install the Browser Runtime component. It is downloaded when you ask for it and checked against its hash — never bundled with the app — and you can remove it again from Tools → Components.
Only http and https load. The rule covers every page change, not just the address you type: if a page tries to move to
file://,javascript:ordata:— by a redirect, a script, a pop-up or a frame — the move is cancelled, so a page cannot read your files. On Windows the page runs in Chromium's sandbox. The runtime is not yet code-signed. The page's sound is not captured yet: this version is picture only.
Game capture
Capture an exclusive-fullscreen game that ordinary window capture cannot see. Windows only.
- In Sources, click + and choose Game Capture. Read the notice first: it explains the risk in plain words.
- Accept the risk for that one game, then pick the running game from the list.
- Freally Capture loads a small hook into that game and takes its frames at the game's own frame rate.
Read this before you use it. Game capture works by loading a DLL into the game. Anti-cheat and antivirus software may treat that as tampering, and it can get an account banned. Nothing is ever loaded automatically: you agree for one game at a time, and that agreement can never be used for another game — and it never travels inside a shared scene collection. If a game refuses the hook, Freally Capture falls back to ordinary Window Capture with a message rather than failing. HDR games and Direct3D 12 games use Window Capture too. On macOS and Linux this source is not offered.
Replay buffer
Keep the last moments in memory, so a hotkey saves what just happened.
- Click Start Replay Buffer in Controls. Freally Capture keeps the last seconds in a buffer of a fixed size.
- Bind a global Save Replay hotkey in Settings.
- Press it to save the last seconds to a file — without interrupting your stream or your main recording. A "Replay saved" message confirms it.
Teleprompter
A smooth-scrolling script for the person on camera — on a panel in the app, a fullscreen projector that can be mirrored, and the LAN touch panel, all at once.
- Open the teleprompter from Tools, type or paste your script, and set the speed and font. Pace it in characters per second, or switch to BPM (50–250 beats per minute) to read lyrics in time with music; either change re-paces a running scroll.
- Pause chips: type
--for a beat or--Nfor an N-second hold and it becomes a single chip — the cursor steps over it, one Delete or Backspace removes it, and copy and paste keep it whole. - Start countdown: arm an optional 3-2-1 lead-in, shown on both the operator's preview and the projector, so the reader has a beat before the text moves.
- Open the projector for the reader (mirror mode flips it for beam-splitter glass). Opening it closes the operator window, so you can run the stream from the main window while they read; with a countdown armed, the projector goes back to the top, counts down and plays. Play, pause, stop, rewind, fast-forward and restart from the on-screen controls, a hotkey, MIDI, OSC or the LAN panel — every control stays in step.
- Read aloud previews the script with your system's own speech: Windows' built-in voices, macOS's, and on Linux
spd-sayorespeak-ngwhere installed. No speech engine is bundled. - Autocomplete suggests words and phrases in light grey as you type; press Tab to accept. Each of the 18 languages has its own dictionary on your computer, loaded only for the language you are writing in.
Remote control
Drive the studio from a Stream Deck or a Companion-style controller — off by default, password-protected, on your own computer.
- Open Settings → Remote Control, turn on the WebSocket API (off by default), and set a password.
- It listens on
127.0.0.1— this computer only — unless you explicitly allow your network. - Point a Companion or Stream Deck client at the address shown. Switch scenes, run transitions, mute and unmute, start and stop recording, and save replays from hardware buttons.
Remote guests and show production
Turn a remote-guest session into a produced show: up to eight guests, drawing on the live program, a green room, private cues, each guest's connection at a glance, and an automatic grid. Everything here is off or unbound by default, and nothing connects until you invite someone.
Multi-guest sessions
- Start a remote-guest session and share the invite link or its QR code: you plus up to eight guests, a gallery of one to nine. Each guest is a tile with their own mute controls, connection quality, cue channel and one-click seat on air.
- A guest opens the link in a web browser — nothing to install — and taps Join to send their camera and microphone. A guest who has Freally Capture can open the same invite in the app instead. An invite expires after the time you choose.
Note: Pictures and sound go directly between you and each guest, peer to peer and encrypted in transit; only the connection handshake crosses a public signalling service. Sessions are tested at four guests; more depends on your bandwidth and processor.
Telestrator: draw on the live program
- Open the Telestrator and pick a tool — Pen, Highlighter, Arrow or Ellipse — then draw straight onto the program. Your marks are part of the picture the moment you draw them, so they appear in the recording and the stream, not just your preview.
- Let marks Fade after a while, or switch to Whiteboard mode to Keep them until you clear them. Drawing follows a tablet's pressure, and Clear marks can be bound to a hotkey (unbound by default).
The green room
- Turn on the Green room and new guests wait off air while you check their camera and microphone in the Green-room preview. When they are ready, click Seat on air. The guest sees a "you're in the green room" banner, in the app or on the web page.
Cue and talk
- Send a guest a private Cue — with presets such as 30 seconds, Wrap up, You're next and Speak up — over the session's existing peer-to-peer channel. The guest sees it with a live countdown, never in the program.
The connection-quality dashboard
- Watch each guest's connection live — round-trip time, packet loss, the resolution and frame rate you receive, and jitter — with a green, amber or red badge and a small history graph, so a weakening connection shows before your viewers notice.
Automatic guest grids
- Turn on Auto-grid to keep seated guests in a tidy grid of one to nine that rearranges itself as guests join, leave or are seated, or press the arrange button to do it now. Each seat publishes its guest's name as a
{{guestN}}variable, so a title source becomes a nameplate that updates by itself.
Studio management and workflow
Make a whole layout portable and shareable, keep named versions of your scenes, theme the app, and put your favourite actions one tap away — all on your computer, with no server.
Scene packs and versions
- Open the workspace dialog from Scene Collection → Manage Scene Collections…: the pack, compare, snapshot, backup and dock-layout tools are all there.
- Click Export pack… to bundle the current collection and its files (images, media, LUTs, masks, fonts) into one portable
.fcappack. Web addresses and network paths are listed as external rather than bundled, and fonts are flagged for their licences. - Click Import pack… and pick a
.fcappack: it arrives as a new collection, finds its files on this computer, and switches to it. - Click Compare & merge… to compare the current collection with another collection, a pack or a snapshot. Review the added, removed and changed scenes, sources, transforms, filters and visibility, then pick exactly which changes to bring in. Picking a scene brings the sources it uses.
- Click Snapshots…, name a checkpoint and choose Save snapshot. Restore brings it back later — your current layout is saved as a snapshot first, so a restore is never one-way. Up to 50 snapshots are kept, with their disk use shown.
Tip: Snapshots are named history beside autosave and undo. Take one before a risky change, and you always have a labelled point to come back to.
Backup, restore and portable mode
- In the workspace dialog, click Backup & restore…, then Export backup… to save everything — settings, profiles and scene collections — in one
.fcapbackupfile. - On a new computer, click Restore from backup…, tick what to bring in (Settings, Scene collections, Profiles) and choose Restore selected. Restart Freally Capture afterwards to load the restored collections and profiles.
- To run from a USB stick, put a file called
freally-portable.txtbeside the program: all of its data then lives in the program's folder instead of your user profile. Settings → About shows whether portable mode is on and where the data is.
Note: Stream keys and passwords are never written into a backup — enter them again after restoring.
Themes, layouts and quick actions
- Open Settings → Appearance and pick the Custom theme to edit the palette, with live contrast warnings, then Export .fctheme… or Import .fctheme… to share it.
- In the workspace dialog's Dock layouts, save the current arrangement under a name and click a saved layout to switch to it.
- In Settings, type in Search settings… to jump to any setting; a marker shows which categories you have changed since you opened it.
- Choose Tools → Quick actions… to open the button grid. Click Edit, then Add button, set each button's label and color, and add pages. A button can switch a scene, run a macro, play a soundboard pad or run a studio command.
Tip: Quick-action buttons run the same studio commands as hotkeys, and the grid is shared with the LAN touch panel: set it up once and it is on your phone too.
Settings
Profiles, scene collections, hotkeys and language. Everything is free today, so there is nothing to activate. Settings is one window with categories — General, Appearance, Streaming, Output, Replay, Hotkeys, Network, Accessibility and About — opened from the menu bar (File, Edit, View, Docks, Profile, Scene Collection, Tools and Help).
- Apply means apply. The Settings window edits a copy: nothing changes until you click Apply or OK, and Cancel puts back exactly what you had, the theme preview included.
- Profiles and scene collections: keep separate setups — "Streaming" and "Local recording", say — and switch between them without restarting, from the Profile and Scene Collection menus.
- Hotkeys: bind every action from a list that cannot clash — choose a shortcut for one action and it disappears from every other action's list, so two features never share a key. None frees it again.
- Accessibility: choose the mixer's meter colors, including a color-blind-safe set. The whole app works from the keyboard, and screen readers announce going live, recording, reconnecting and dropped frames.
- Language: choose one of 18 languages; the app changes at once, and Arabic reads right to left.
Reporting a problem
You decide whether a problem reaches the developer, and you see exactly what would be sent.
- When the app shows an error it caused itself, a Report button appears beside it.
- After a crash, the next launch offers Report or Dismiss.
- Report opens Freally Capture's report page on this site in your browser, with the technical facts already filled in: you can read them, but not change them. Add what you were doing and, if you like, an email address. Nothing is sent unless you press Send there.
- Nothing is ever sent in the background, and Dismiss sends nothing at all.
Privacy and the network
Freally Capture has no account and no telemetry, and there is no cloud service of ours. Here is exactly what goes online, and what does not.
- No account, no telemetry. The app never asks you to sign in and never sends your scenes, recordings or any usage data anywhere.
- Your stream goes straight to the platform. It travels from your computer to the services you set up — there is no relay server of ours.
- Your recordings stay on your computer, in the folder you choose. Nothing is uploaded.
- Your stream keys stay on your computer, shown masked and sent only to the service you stream to.
- Remote guests connect peer to peer. Only the session's handshake crosses a public signalling service, and only when you start a session.
- A chat overlay reads public chat from the channel you point it at, the way a signed-out viewer would — no account, key or sign-in.
- Two components are downloaded only when you first need them: ffmpeg, for the codecs the platforms require, and the browser runtime, for the browser source. Each comes from its own publisher and is checked before use.
- An update check fetches one small file once per launch, and when you choose Check for updates…. Nothing about you or your computer is sent with it, and nothing is installed unless you say yes.
- A problem report is sent only when you press Send on the report page, after you have read what it holds (see Reporting a problem).
- No AI. Every filter — noise suppression, chroma key, tone-mapping — is classic signal processing. The app contains no machine-learning model and downloads none.