Forum Discussion
Deleting used source screen recording
Hi Wendy,
Thanks for reaching out!
You can only remove unused screen recordings from a Storyline 360 project file.
Based on your description, it looks like the slides generated from the screen recording are still in use which is why you can't delete the recording. There isn't a way to modify the screen recording's availability to prevent other authors from accessing them. Can I ask what is the reason behind wanting to prevent other authors from accessing the screen recording so we can check if any workarounds are available?
Thank you for the reply. The reason for not wanting authors to access the screen recording is because the simulations are for two different clients using the same product, thus the same callouts and steps. However, they each have the system customized to match their company logo and company colors. We don't want the 2nd company to have the ability to insert the screen recordings that were captured from the 1st company.
Thanks for the additional information! There isn't a way to delete screen recordings that are in use in a Storyline 360 project so I filed a feature request on your behalf and shared the details in this post. Here's a quick look at how we manage feature requests for your reference!
I have a similar problem with a slight variant. The recording is in use. Articulate reports it as corrupted. After asking Articulate to recover the corrupted assets. it says it cannot recover it. I go to remove it manually, it is "in use". I proceed to see the content by creating a new scene with it to identify. It does not create a new scene, , the alledged recording is empty. Articulate does not report that it cannot generate the scene, it does not report that the recording is empty, it also does not say when you access it, that it is corrupt or damaged, and since I cannot identify where it is in the file. I cannot delete or deassociate its content.
I am assuming that this feature to remove the "in use" recording is not implemented. I have the latest version installed of articulate.
Thanks for sharing that, MadelineThen.
Just chiming in here alongside Wendy’s original thread, since your scenario highlights a different angle.
I see what you’re running into, especially with the recording being marked as “in use” but not actually generating any usable content or giving clear feedback on where it’s referenced. That can make it really difficult to clean up the project.
At the moment, this falls under a known limitation where recordings can’t be removed if they’re considered in use, even if they’re corrupted or not accessible. There also isn’t a way to trace exactly where that recording is linked within the file.
I’ve shared your use case with our product team. Your example around corrupted or “ghost” recordings that can’t be identified or removed adds helpful context to that request.
