Framewell's file tools use a browser File object and a local object URL to preview a video you select. The frame exporter draws a decoded frame to a canvas. The inspector reads browser-reported properties. The clip tool uses the browser media capture and MediaRecorder APIs to record a short playback range.
The selected video is handled in the tab
The tool code does not send the video file to Framewell servers or store it in a Framewell account. A generated PNG or WebM is created in the browser and follows your normal download settings. Closing the page releases the page's working object URLs under normal browser behavior.
Local does not mean the page is network-free
Your browser still requests the page, styles, scripts, and images from the hosting infrastructure. All pages load Google's Funding Choices consent service, and selected informational pages also load AdSense. Those services may receive routine technical request information and may use cookies or similar identifiers under their own policies. See the Privacy Policy and Cookie Policy.
Browser memory and codec support
Video decoding can use much more memory than the compressed file size. High resolutions and long recordings can fail on phones or low-memory devices. Browser codec support also varies; if a file will not play, the tool cannot process it.
Use an approved workflow for sensitive media
If a recording belongs to an organization with a required managed editor, secure workstation, or documented chain of custody, use that approved workflow. Do not select confidential media in a tool unless the browser and device meet your own requirements.