Niobium
Niobium extends the Python Selenium client with nice features.
Why Niobium
Selenium is a good tool for web automation, but sometimes it's hard to write a clean automation script.
With Niobium, you can keep using Selenium while simplifying your scripts. For example, Niobium adds a new method that uses image recognition to interact with the webpage.
The goal of Niobium is not to replace Selenium. We only want to add to Selenium the functions we will love to see in Selenium natively.
Niobium philosophy is to keep as simple as possible.
Installation
Niobium is available on Pypi, so simply use pip.
pip install niobium
Getting Started
In order to use Niobium, you just need to import it in your script. Selenium will be automatically extended.
import niobium
from selenium import webdriver
driver = webdriver.Firefox()
driver.implicitly_wait(10)
driver.get("https://www.python.org/")
driver.find_image("logo_python.png")
driver.quit()
In order to avoid warning with your linter, you can import selenium from niobium.
from niobium import selenium
driver = selenium.webdriver.Firefox()
...
or simply disable the warning, like in this example for flake8
import niobium # noqa: F401
from selenium import webdriver
driver = webdriver.Firefox()
...
If you use pytest and especially pytest-selenium, just import niobium in your conftest.py.
Documentation
https://niobium.readthedocs.io/
Warnings
Some features implemented in Niobium are here only to help you when there is no other easy solution. If you do a bad usage of Niobium features, it can result to a bad performance in your script, or it will be difficult to maintain it. Please read the documentation in order to know the special warnings for the use of these features.
Niobium do not modify the Selenium library package. The patches are only applied at runtime. This is the reason why the autocompletion is not updated correctly.
Release files for niobium 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| niobium-1.0.1.tar.gz | 11.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| niobium-1.0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 22.6 kB
Release files / niobium-1.0.1.tar.gz
| Download URL | niobium-1.0.1.tar.gz |
|---|---|
| Size | 11.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0416d64563225802bb8d87874331a503d41caaa78eb093a4885a6c1c15972c06
|
|
BLAKE2b-256 checksum How to use checksums |
34d89d1543fbf0f4d77bfd7ee51759b48cf7b6922806b40a6694831cc219c308
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 4, 2026.
Transparency logRelease files / niobium-1.0.1-py3-none-any.whl
| Download URL | niobium-1.0.1-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f1ce9b4cdc78775ad38703298c439d2e4e132a013b430bb7dfdb3af99609f40c
|
|
BLAKE2b-256 checksum How to use checksums |
6b7d4ee02d28a17872b583807a25235f4a07e3190de76da2d0086fa09dcc915f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 4, 2026.
Transparency log