Snapsht 🦓 - Capture full-page screenshots with ease, every time.
snapsht is designed to provide users a command-line interface to take full screen scrolling screenshots of webpages.
Snapsht can be helpful for developers and designers who need to take full-page screenshots of websites for testing or design purposes. They can quickly and easily capture screenshots of entire web pages, even those that extend beyond the visible area of the screen.
For developers, snapsht can be useful for testing web page layouts and responsiveness across different screen sizes and devices. It can also be helpful for debugging issues that only occur on specific parts of a web page that are not visible on the screen.
snapsht can be useful for creating visual mockups or capturing design inspiration from existing websites. It can also be helpful for reviewing and sharing design feedback with clients or team members.
Overall, snapsht can save time and effort for developers and designers who need to capture full-page screenshots of websites on a regular basis.
I hope you find it useful.
Configuration
The application requires you to have the chromium driver available. If you dont have it on the PATH run the setup command which will download the correct binary on your system and use it. You must also have the chrome browser installed.
Installation
Install the snapsht python package directly from pypi.
pip install snapsht
I would recommend using pipx instead of pip to install cli applications on you machine.
Usage
Usage: snapsht [OPTIONS] COMMAND [ARGS]...
🦓 Capture full-page screenshots with ease, every time.
Options:
--version Show the version and exit.
--help Show this message and exit.
Commands:
click 🎴 Take a full page scrolling screenshot and save it to disk.
setup ⏬ Download missing chromium driver.
Note
Taking screenshots automatically is tough. If you do get errors and dont know why, try adding the --debug flag to the click command.
Thank you!
Please feel to create issues or request for features. More options and commands will be added to the application in the near future.
Metadata
Release files for snapsht 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| snapsht-1.0.3.tar.gz | 5.6 kB | Without provenance | Details for snapsht-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| snapsht-1.0.3-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for snapsht-1.0.3-py2.py3-none-any.whl |
Total release size: 11.5 kB
Release files / snapsht-1.0.3.tar.gz
| Download URL | snapsht-1.0.3.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9692f2adfcae47fab421827548457365dfb3cd85897b0a19b3e56e36c05250b0
|
|
BLAKE2b-256 checksum How to use checksums |
ad20b6da3c6534ecf35028cc3686967c592356f6a59a87771c5d2a1a1db2b4a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.16
|
Release files / snapsht-1.0.3-py2.py3-none-any.whl
| Download URL | snapsht-1.0.3-py2.py3-none-any.whl |
|---|---|
| Size | 5.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
4da5bc85c6ef02979471ca58ee67bf5fa4cbcbfde86e3e559d1ef5419d874b3b
|
|
BLAKE2b-256 checksum How to use checksums |
34a0f3ca3870cc013c2485276d05dfb0d63ef51a3f4dbbb4a667fa4990b70855
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.16
|
Security for snapsht 1.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.