# Video play, pause, resume and stop all works - Just sharing a working module

**URL:** <https://community.thunkable.com/t/video-play-pause-resume-and-stop-all-works-just-sharing-a-working-module/4107792>\
**Category:** Issues / Bugs\
**Created:** [October 14, 2025, 10:56pm UTC](https://community.thunkable.com/t/video-play-pause-resume-and-stop-all-works-just-sharing-a-working-module/4107792 "2025-10-14T22:56:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![anandavardhana57zwwl](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@anandavardhana57zwwl](https://community.thunkable.com/u/anandavardhana57zwwl)\
**Post date:** [October 14, 2025, 10:56pm UTC](https://community.thunkable.com/t/video-play-pause-resume-and-stop-all-works-just-sharing-a-working-module/4107792/1 "2025-10-14T22:56:59Z")

</div>

Video blocks documentation is not good and the video blocks do not jell logically so it took some effort and ChatGPT to figure it out. I saw lot of questions on how to get this to work and no one cohesive answer. So thought of sharing my program and give back to the community. Enjoy

> **[Thunkable](https://x.thunkable.com/copy/1e5895be4fc0bc1dbcce62ae3b21dd30)**

PS: The Video component, Play button can be enabled or not it does not matter. Since you need the URL to stop you cannot upload the URL in the property window. This the best I could come up with. I am no expert, if someone can improve on this and stream line it all the better. The audio does not work with WebPreview, on the device both audio and video works perfectly.

---

<div class="post-metadata">

**Author:** ![ioannis](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/ioannis/32/146956_2.png) [@ioannis](https://community.thunkable.com/u/ioannis)\
**Post date:** [October 15, 2025, 11:02am UTC](https://community.thunkable.com/t/video-play-pause-resume-and-stop-all-works-just-sharing-a-working-module/4107792/2 "2025-10-15T11:02:24Z")

</div>

Hi @anandavardhana57zwwl  
We were able to replicate the issue on the Web and have flagged it to our engineering team.  
Will provide an update as soon as possible.  
On mobile, it should work,
