A GitHub Action that captures a webpage and converts it into an animated GIF or WebP file.
website-to-gif is a GitHub Action that converts webpages into animated GIFs or WebP files. It automates the process of capturing screenshots while scrolling or at timed intervals, then stitches them together into a single animated file. This solves the problem of manually creating visual demos or documentation assets for projects.
Developers and technical writers who need to generate animated previews of web applications for README files, documentation, or marketing materials directly within their GitHub workflows.
Developers choose website-to-gif because it integrates natively with GitHub Actions, requires no external services, and offers fine-grained control over the capture process. Its open-source nature and configurability make it a flexible alternative to manual or paid screenshot-to-video tools.
GitHub Action to turn your website into a GIF :camera:
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Captures sequential frames through scrolling or timed intervals, with configurable parameters like scroll_step and time_per_frame, enabling hands-free demo generation.
Supports both GIF and WebP formats, allowing optimization for file size and quality, though the README notes WebP can be slow for lossless rendering.
Includes a ready-to-use workflow example for automatic generation and commit, making it easy to embed in existing GitHub repositories without external tools.
Offers numerous inputs like window size, scroll steps, and resizing filters, providing fine-grained control over the capture process and output appearance.
The README explicitly warns that WebP rendering takes 'a lot' of time for lossless quality, which can slow down CI/CD pipelines and increase resource usage.
Only outputs GIF and WebP, lacking support for more common video formats like MP4 that are often preferred for compatibility and compression in modern applications.
Requires the save_path to exist beforehand, as the action won't create directories, adding setup overhead and potential for errors in workflow configuration.