PyOTP - The Python One-Time Password Library¶
PyOTP is a Python library for generating and verifying one-time passwords. It can be used to implement two-factor (2FA) or multi-factor (MFA) authentication methods in web applications and in other systems that require users to log in.
Open MFA standards are defined in RFC 4226 (HOTP: An HMAC-Based One-Time Password Algorithm) and in RFC 6238 (TOTP: Time-Based One-Time Password Algorithm). PyOTP implements server-side support for both of these standards. Client-side support can be enabled by sending authentication codes to users over SMS or email (HOTP) or, for TOTP, by instructing users to use Google Authenticator, Authy, or another compatible app. Users can set up auth tokens in their apps easily by using their phone camera to scan otpauth:// QR codes provided by PyOTP.
Implementers should read and follow the HOTP security requirements and TOTP security considerations sections of the relevant RFCs. At minimum, application implementers should follow this checklist:
Ensure transport confidentiality by using HTTPS
Ensure HOTP/TOTP secret confidentiality by storing secrets in a controlled access database
Deny replay attacks by persisting the last accepted OTP counter for each credential and rejecting reused counters. For TOTP, use
verify_and_get_timecode()as described in Preventing replay attacks below.Throttle (rate limit) brute-force attacks against your application’s login functionality (see RFC 4226, section 7.3 and NIST SP 800-63B, section 3.2.2)
When implementing a “greenfield” application, consider supporting FIDO U2F/WebAuthn in addition to or instead of HOTP/TOTP. U2F uses asymmetric cryptography to avoid using a shared secret design, which strengthens your MFA solution against server-side attacks. Hardware U2F also sequesters the client secret in a dedicated single-purpose device, which strengthens your clients against client-side attacks. And by automating scoping of credentials to relying party IDs (application origin/domain names), U2F adds protection against phishing attacks. One implementation of FIDO U2F/WebAuthn is PyOTP’s sister project, PyWARP.
We also recommend that implementers read and follow the following resources:
NIST SP 800-63 Digital Identity Guidelines, including sections 3.1.4 (Single-Factor OTP) and 3.1.5 (Multi-Factor OTPs), for an in-depth discussion of authentication
The OWASP Authentication Cheat Sheet for a high level overview of authentication best practices
The OWASP Multifactor Authentication Cheat Sheet for an intermediate level practical architecture guide to MFA
Quick overview of using One Time Passwords on your phone¶
OTPs involve a shared secret, stored both on the phone and the server
OTPs can be generated on a phone without internet connectivity
OTPs should always be used as a second factor of authentication (if your phone is lost, you account is still secured with a password)
Google Authenticator and other OTP client apps allow you to store multiple OTP secrets and provision those using a QR Code
Installation¶
pip install pyotp
Usage¶
Time-based OTPs¶
import pyotp
totp = pyotp.TOTP('base32secret32323232323232')
totp.now() # Current OTP; changes with the clock.
# A fixed Unix timestamp makes these example outputs reproducible.
totp.at(1234567890) # => '763850'
totp.verify('763850', for_time=1234567890) # => True
totp.verify('763850', for_time=1234567920) # => False
Preventing replay attacks¶
TOTP.verify() and TOTP.verify_and_get_timecode() are stateless: they can accept the same OTP repeatedly while
it remains valid. To prevent reuse, call verify_and_get_timecode() and persist its returned timecode for each
credential in a database shared by all application workers. The timecode identifies the matching TOTP interval;
it is not the wall-clock timestamp when verification occurred. Reject a timecode that is less than or equal to the
last accepted timecode.
verify_and_get_timecode() raises pyotp.OTPVerificationError (a subclass of pyotp.PyOTPError) if the OTP
does not match within the allowed window. Successful verification always returns an integer timecode.
The check and update must be atomic, so two concurrent requests cannot both accept the same timecode. For example,
the following function uses a sqlite3.Connection named db and a totp_credentials table with one existing
row per credential, an id primary key, and a nullable integer last_timecode column. Initialize
last_timecode to NULL for a new credential. totp and credential_id must refer to the same credential.
import pyotp
def verify_totp_once(db, credential_id, totp, otp):
try:
matched_timecode = totp.verify_and_get_timecode(otp)
except pyotp.OTPVerificationError:
return False
with db:
updated = db.execute(
"UPDATE totp_credentials SET last_timecode = ? "
"WHERE id = ? AND (last_timecode IS NULL OR last_timecode < ?)",
(matched_timecode, credential_id, matched_timecode),
)
return updated.rowcount == 1
Grant authentication only when this function returns True, after the database transaction has committed.
If you enable valid_window, persist the returned matching timecode, which may differ from the server’s current timecode.
Warning
For both HOTP and TOTP, do not use the raw submitted OTP, or a hash of that raw value, as the replay-detection key.
PyOTP applies Unicode NFKC normalization when comparing OTPs: for example, 123456 and 123456 are treated
as the same code, but their raw strings and hashes differ. An attacker could submit another spelling of an
already-used code to bypass such a check. Track the accepted counter instead.
Counter-based OTPs¶
import pyotp
hotp = pyotp.HOTP('base32secret32323232323232')
hotp.at(0) # => '995369'
hotp.at(1) # => '511453'
hotp.at(1401) # => '666948'
# OTP verified with a counter
hotp.verify('666948', 1401) # => True
hotp.verify('666948', 1402) # => False
Generating a Secret Key¶
A helper function is provided to generate a 32-character base32 secret, compatible with Google Authenticator and other OTP apps:
pyotp.random_base32()
Some applications want the secret key to be formatted as a hex-encoded string:
pyotp.random_hex() # returns a 40-character hex-encoded secret
Google Authenticator Compatible¶
PyOTP works with the Google Authenticator iPhone and Android app, as well as other OTP apps like Authy. PyOTP includes the ability to generate provisioning URIs for use with the QR Code scanner built into these MFA client apps:
pyotp.totp.TOTP('JBSWY3DPEHPK3PXPJBSWY3DP').provisioning_uri(name='alice@google.com', issuer_name='Secure App')
>>> 'otpauth://totp/Secure%20App:alice%40google.com?secret=JBSWY3DPEHPK3PXPJBSWY3DP&issuer=Secure%20App'
pyotp.hotp.HOTP('JBSWY3DPEHPK3PXPJBSWY3DP').provisioning_uri(name="alice@google.com", issuer_name="Secure App", initial_count=0)
>>> 'otpauth://hotp/Secure%20App:alice%40google.com?secret=JBSWY3DPEHPK3PXPJBSWY3DP&issuer=Secure%20App&counter=0'
This URL can then be rendered as a QR Code (for example, using https://github.com/soldair/node-qrcode) which can then be scanned and added to the users list of OTP credentials.
Parsing these URLs is also supported:
pyotp.parse_uri('otpauth://totp/Secure%20App:alice%40google.com?secret=JBSWY3DPEHPK3PXPJBSWY3DP&issuer=Secure%20App')
>>> <pyotp.totp.TOTP object at 0xFFFFFFFF>
pyotp.parse_uri('otpauth://hotp/Secure%20App:alice%40google.com?secret=JBSWY3DPEHPK3PXPJBSWY3DP&issuer=Secure%20App&counter=0')
>>> <pyotp.hotp.HOTP object at 0xFFFFFFFF>
Working example¶
Scan the following barcode with your phone’s OTP app (e.g. Google Authenticator):
Now run the following and compare the output:
import pyotp
totp = pyotp.TOTP("JBSWY3DPEHPK3PXPJBSWY3DP")
print("Current OTP:", totp.now())
Third-party contributions¶
The following third-party contributions are not described by a standard, not officially supported, and provided for reference only:
pyotp.contrib.Steam(): An implementation of Steam TOTP. Uses the same API as pyotp.TOTP().
Links¶
ROTP - Original Ruby OTP library by Mark Percival
For new applications:
Versioning¶
This package follows the Semantic Versioning 2.0.0 standard. To control changes, it is recommended that application developers pin the package version and manage it using pip-tools or similar. For library developers, pinning the major version is recommended.
API documentation¶
- pyotp.parse_uri(uri: str) OTP[source]¶
Parses the provisioning URI for the OTP; works for either TOTP or HOTP.
- Parameters:
uri – the hotp/totp URI to parse
- Returns:
OTP object
- class pyotp.totp.TOTP(s: str, *, digits: int = 6, digest: Any | None = None, name: str | None = None, issuer: str | None = None, interval: int = 30)[source]¶
Handler for time-based OTP counters.
- at(for_time: int | float | datetime, *, counter_offset: int = 0) str[source]¶
Accepts a Unix timestamp (int or float) or a datetime object.
Unix timestamps are measured in seconds since 1970-01-01 00:00:00 UTC. Prefer Unix timestamps or timezone-aware UTC datetimes. Naive datetimes are interpreted as local time, respecting
fold.To get the time until the next timecode change (seconds until the current OTP expires), use this instead:
totp = pyotp.TOTP(...) time_remaining = totp.interval - time.time() % totp.interval
- Parameters:
for_time – the time to generate an OTP for
counter_offset – the amount of ticks to add to the time counter
- Returns:
OTP value
- Raises:
ValueError – if for_time is before the Unix epoch or after year 9999 in UTC
- now() str[source]¶
Generate the current time OTP
- Returns:
OTP value
- Raises:
ValueError – if the current time is before the Unix epoch or after year 9999 in UTC
- provisioning_uri(*, name: str | None = None, issuer_name: str | None = None, **kwargs: Any) str[source]¶
Returns the provisioning URI for the OTP. This can then be encoded in a QR Code and used to provision an OTP app like Google Authenticator.
- timecode(for_time: int | float | datetime) int[source]¶
Converts a Unix timestamp (int or float) or a datetime object to the corresponding counter value (timecode).
Unix timestamps are measured in seconds since 1970-01-01 00:00:00 UTC. Prefer Unix timestamps or timezone-aware UTC datetimes. Naive datetimes are interpreted as local time, using
foldto distinguish repeated clock times. Subsecond precision is ignored.- Raises:
ValueError – if for_time is before the Unix epoch or after year 9999 in UTC
- verify(otp: str, *, for_time: int | float | datetime | None = None, valid_window: int = 0) bool[source]¶
Verifies the OTP passed in against the current time OTP.
Unix timestamps are measured in seconds since 1970-01-01 00:00:00 UTC. Prefer Unix timestamps or timezone-aware UTC datetimes. Naive datetimes are interpreted as local time, respecting
fold.- Parameters:
otp – the OTP to check against
for_time – Unix timestamp (int or float) or datetime to check OTP at (defaults to now)
valid_window – extends the validity to this many counter ticks before and after the current one
- Returns:
True if verification succeeded, False otherwise
- Raises:
ValueError – if for_time is before the Unix epoch or after year 9999 in UTC
- verify_and_get_timecode(otp: str, *, for_time: int | float | datetime | None = None, valid_window: int = 0) int[source]¶
Verifies the OTP passed in against the current time OTP and returns the matching timecode.
Caution
Note the signature difference between this method and
verify(): this method raisesOTPVerificationErroron an OTP mismatch, whileverify()returnsFalse.This is useful when callers need to prevent TOTP reuse. An application can store the timecode from the last successful authentication and reject future OTPs whose matching timecode is not greater than the stored one.
Unix timestamps are measured in seconds since 1970-01-01 00:00:00 UTC. Prefer Unix timestamps or timezone-aware UTC datetimes. Naive datetimes are interpreted as local time, respecting
fold.- Parameters:
otp – the OTP to check against
for_time – Unix timestamp (int or float) or datetime to check OTP at (defaults to now)
valid_window – extends the validity to this counter ticks before and after the current one
- Returns:
matching timecode if verification succeeded
- Raises:
pyotp.exceptions.OTPVerificationError – if the OTP does not match within the valid window
ValueError – if valid_window is negative or for_time is before the Unix epoch or after year 9999 in UTC
- class pyotp.hotp.HOTP(s: str, *, digits: int = 6, digest: Any | None = None, name: str | None = None, issuer: str | None = None, initial_count: int = 0)[source]¶
Handler for HMAC-based OTP counters.
- at(count: int) str[source]¶
Generates the OTP for the given count.
- Parameters:
count – the OTP HMAC counter
- Returns:
OTP
- provisioning_uri(*, name: str | None = None, initial_count: int | None = None, issuer_name: str | None = None, **kwargs: Any) str[source]¶
Returns the provisioning URI for the OTP. This can then be encoded in a QR Code and used to provision an OTP app like Google Authenticator.
- Parameters:
name – name of the user account
initial_count – starting HMAC counter value, defaults to 0
issuer_name – the name of the OTP issuer; this will be the organization title of the OTP entry in Authenticator
- Returns:
provisioning URI
- exception pyotp.exceptions.OTPVerificationError[source]¶
Bases:
PyOTPErrorRaised when an OTP does not match any permitted counter.
- exception pyotp.exceptions.PyOTPError[source]¶
Bases:
ExceptionBase class for PyOTP-specific errors.
- pyotp.utils.build_uri(secret: str, name: str, initial_count: int | None = None, issuer: str | None = None, algorithm: str | None = None, digits: int | None = None, period: int | None = None, **kwargs: str) str[source]¶
Returns the provisioning URI for the OTP; works for either TOTP or HOTP.
This can then be encoded in a QR Code and used to provision the Google Authenticator app.
For module-internal use.
- Parameters:
secret – the hotp/totp secret used to generate the URI
name – name of the account
initial_count – starting counter value, defaults to None. If none, the OTP type will be assumed as TOTP.
issuer – the name of the OTP issuer; this will be the organization title of the OTP entry in Authenticator
algorithm – the algorithm used in the OTP generation.
digits – the length of the OTP generated code.
period – the number of seconds the OTP generator is set to expire every code.
kwargs – other query string parameters to include in the URI
- Returns:
provisioning uri
- pyotp.utils.strings_equal(s1: str, s2: str) bool[source]¶
Timing-attack resistant string comparison.
Normal comparison using == will short-circuit on the first mismatching character. This avoids that by scanning the whole string, though we still reveal to a timing attack whether the strings are the same length.
Returns False if either input exceeds 1024 Unicode code points. The limit is checked before normalization to bound its CPU cost and mitigate CVE-2026-3276.
Change log¶
- Release Notes
- Changes for v2.12.0 (2026-11-15)
- Changes for v2.11.2 (2026-11-14)
- Changes for v2.11.1 (2026-11-14)
- Changes for v2.11.0 (2026-11-14)
- Changes for v2.10.0 (2026-06-13)
- Changes for v2.9.0 (2023-07-27)
- Changes for v2.8.0 (2022-12-13)
- Changes for v2.7.0 (2022-09-11)
- Changes for v2.6.0 (2021-02-04)
- Changes for v2.5.1 (2021-01-29)
- Changes for v2.5.0 (2021-01-29)
- Changes for v2.4.1 (2020-10-16)
- Changes for v2.4.0 (2020-07-29)
- Changes for v2.3.0 (2019-07-26)
- Changes for v2.2.8 (2019-07-26)
- Changes for v2.2.7 (2018-11-05)
- Changes for v2.2.6 (2017-06-10)
- Changes for v2.2.5 (2017-06-03)
- Changes for v2.2.4 (2017-01-04)
- Changes for v2.2.3 (2017-01-04)
- Changes for v2.2.2 (2017-01-04)
- Changes for v2.2.1 (2016-08-30)
- Changes for v2.2.0 (2016-08-30)