Record SDK
Embed screen recording in your product with Zight’s SDK.
Add in-app screen recording with a few lines of code while Zight handles uploading, hosting, playback, transcripts, and share links
A few lines of code · most integrations done inside a day
Your product, your button. The recorder, the hosting and the transcript are ours.
Trusted by 5m+ people who would rather show than tell
What is the Zight Record SDK?
The Zight Record SDK embeds Zight's screen recorder inside another product, in a few lines of code. Users record from your interface without leaving it, and Zight handles capture, upload, hosting, playback and the transcript. Lucid ships it in Lucidchart and Lucidspark; Jira uses it to attach recordings to tickets.
What you are not building
The estimate is never the recorder
Teams scope "add video recording" as a UI problem. The recorder is a fortnight; everything behind it is the quarter.
A recorder you did not build
Capture UI, permissions, device pickers, countdown, pause, stop. Every product that has tried to build this has discovered the browser makes the last 20% expensive.
Somewhere for the video to go
The upload, the transcode, the storage, the player, the share link. The recorder is the part people estimate; this is the part that turns into a quarter of infrastructure work.
It arrives as more than a file
What your user records comes back with a transcript, an AI title and a summary, the same as any other Zight recording — so the thing landing in your app is searchable text, not an opaque blob.
A day, not a quarter
A few lines of code, and the pilot is usually done inside a day. The comparison is not against another SDK — it is against the roadmap slot you were going to spend building this.
Already shipping it
Two products you have used
Lucid
Zight screen recording runs natively inside Lucidchart and Lucidspark, so a comment on a diagram can be a recording of someone talking through it.
See the Lucid integrationJira
Recordings attach straight to tickets, which is the difference between a bug report you can act on and three paragraphs describing a screen.
See the Jira integrationWhat people embed it for
Four flows that stop working when the user has to leave
Bug reports inside your product
A "Report a bug" button that returns what the user did rather than what they remember doing.
EngineeringSupport without the screenshot thread
Let someone show you the problem from inside the session they are already in, signed in as themselves.
Customer SupportFeedback and review in context
Comments recorded against the thing being reviewed — the design, the document, the diagram — not typed somewhere else about it.
DesignOnboarding your users record themselves
Customer success teams collecting walkthroughs from accounts instead of scheduling a call to watch one.
Customer SuccessFAQ
Questions a developer asks first
It is a way to put Zight’s screen recorder inside your own product. Your users record from your interface, and the recording is captured, hosted, transcribed and given a share link by Zight rather than by infrastructure you build and run.
A few lines of code, and implementation usually takes less than a day. The setup guide in the help centre is the reference; talk to us and we will point you at the right starting configuration.
Lucid ships it natively in Lucidchart and Lucidspark, and Jira uses it to attach recordings to tickets. Both are also full Zight integrations, so you can see the finished shape on those pages.
The recording experience lives inside your product, which is the point of embedding it rather than linking out. Account handling depends on how you configure the integration — that is one of the things worth a conversation before you start.
A hosted recording with a share link, a transcript, an AI-generated title and a summary — the same output as any Zight recording. That means the thing arriving in your app is searchable, not an opaque video file.
A link sends your user somewhere else and hopes they come back. The SDK keeps them in your product, in the session they are already authenticated in, which is why bug-report and feedback flows convert so differently when the recorder is embedded rather than referenced.
Ship the recorder next sprint.
Tell us what your users need to record and we will point you at the right starting configuration.