Base64 . Guru
A virtual teacher who reveals to you the great secrets of Base64
Python Base64 Decode
To decode Base64 to original data, Python provides the b64decode function of the base64 module. In addition, this module also provides the b64encode function, as well as other useful functions to decode Base64 strings using several algorithms specified in RFC 3548.
Usage:
- b64decode(b64) — Discards all invalid characters from b64 and decodes it from Base64 to original data
- b64decode(b64, altchars) — Replaces altchars with +/ from b64 and decodes it from Base64 to original data
- b64decode(b64, altchars, validate) — If validate is set to True the b64 must contain only valid Base64 characters
Arguments:
- b64 (required string) — The Base64 value that should be decoded
- altchars (optional string; default None ) — Two characters that should replace “+” and “/”
- validate (optional bool; default False ; added in Python 3) — Allows to decode only valid Base64 values
Return Values:
Supported Versions:
Changelog:
- Python 3.1:
- Adds the decodebytes function, which Base64 values to bytes
- The function decodestring is deprecated
- ASCII-only Unicode strings are now accepted by the decoding functions of the modern interface
- Adds the a85decode function, which decodes Ascii85 to original data
- Adds the b85decode function, which decodes Base85 to original data
- Any bytes-like objects are now accepted by all decoding functions in the base64 module
Example #1 (print the result):
from base64 import b64decode b64 = 'Z3VydQ==' print(b64decode(b64)) #-> 'guru'
from base64 import b64decode b64 = '4oKsMTAw' print(b64decode(b64).decode('utf-8')) #-> '€100'
from base64 import b64decode b64 = 'PDw_Pz8-Pg==' print(b64decode(b64)) #-> ' '>'
from base64 import b64decode b64 = 'Z 3 V y d Q==' print(b64decode(b64)) #-> b'guru' print(b64decode(b64, None, True)) #-> binascii.Error: Non-base64 digit found
# Python 2.7: TypeError: Incorrect padding # Python 3.6: binascii.Error: Incorrect padding b64decode('a=b')
# Python 2.7 - b64decode() takes at least 1 argument (0 given) # Python 3.6 - b64decode() missing 1 required positional argument: 's' b64decode()
# Python 2.7 - a2b_base64() argument 1 must be string or buffer, not int # Python 3.6 - argument should be a bytes-like object or ASCII string, not 'int' b64decode(123)
Comments (4)
How do I decode this? I tried but it didn’t work. I’m a complete noob I don’t know anything my friends sent me this asking me to try and won’t help. Thank you.
Please seerved seed can someone find the server seed from the Seerved hash (512) String
123188:8681b78514365ed639ae6620e337c6f70a8b87dca580dd3ae9eebf876096b116:123188
123188:0000:123188I want to extract readable text from Base64 files(files can be of any format, like, ppt, pdf, images).
How can i extract readable text?base64 — Base16, Base32, Base64, Base85 Data Encodings¶
This module provides functions for encoding binary data to printable ASCII characters and decoding such encodings back to binary data. It provides encoding and decoding functions for the encodings specified in RFC 4648, which defines the Base16, Base32, and Base64 algorithms, and for the de-facto standard Ascii85 and Base85 encodings.
The RFC 4648 encodings are suitable for encoding binary data so that it can be safely sent by email, used as parts of URLs, or included as part of an HTTP POST request. The encoding algorithm is not the same as the uuencode program.
There are two interfaces provided by this module. The modern interface supports encoding bytes-like objects to ASCII bytes , and decoding bytes-like objects or strings containing ASCII to bytes . Both base-64 alphabets defined in RFC 4648 (normal, and URL- and filesystem-safe) are supported.
The legacy interface does not support decoding from strings, but it does provide functions for encoding and decoding to and from file objects . It only supports the Base64 standard alphabet, and it adds newlines every 76 characters as per RFC 2045. Note that if you are looking for RFC 2045 support you probably want to be looking at the email package instead.
Changed in version 3.3: ASCII-only Unicode strings are now accepted by the decoding functions of the modern interface.
Changed in version 3.4: Any bytes-like objects are now accepted by all encoding and decoding functions in this module. Ascii85/Base85 support added.
The modern interface provides:
base64. b64encode ( s , altchars = None ) ¶
Encode the bytes-like object s using Base64 and return the encoded bytes .
Optional altchars must be a bytes-like object of length 2 which specifies an alternative alphabet for the + and / characters. This allows an application to e.g. generate URL or filesystem safe Base64 strings. The default is None , for which the standard Base64 alphabet is used.
May assert or raise a ValueError if the length of altchars is not 2. Raises a TypeError if altchars is not a bytes-like object .
base64. b64decode ( s , altchars = None , validate = False ) ¶
Decode the Base64 encoded bytes-like object or ASCII string s and return the decoded bytes .
Optional altchars must be a bytes-like object or ASCII string of length 2 which specifies the alternative alphabet used instead of the + and / characters.
A binascii.Error exception is raised if s is incorrectly padded.
If validate is False (the default), characters that are neither in the normal base-64 alphabet nor the alternative alphabet are discarded prior to the padding check. If validate is True , these non-alphabet characters in the input result in a binascii.Error .
For more information about the strict base64 check, see binascii.a2b_base64()
May assert or raise a ValueError if the length of altchars is not 2.
base64. standard_b64encode ( s ) ¶
Encode bytes-like object s using the standard Base64 alphabet and return the encoded bytes .
base64. standard_b64decode ( s ) ¶
Decode bytes-like object or ASCII string s using the standard Base64 alphabet and return the decoded bytes .
base64. urlsafe_b64encode ( s ) ¶
Encode bytes-like object s using the URL- and filesystem-safe alphabet, which substitutes — instead of + and _ instead of / in the standard Base64 alphabet, and return the encoded bytes . The result can still contain = .
base64. urlsafe_b64decode ( s ) ¶
Decode bytes-like object or ASCII string s using the URL- and filesystem-safe alphabet, which substitutes — instead of + and _ instead of / in the standard Base64 alphabet, and return the decoded bytes .
Encode the bytes-like object s using Base32 and return the encoded bytes .
base64. b32decode ( s , casefold = False , map01 = None ) ¶
Decode the Base32 encoded bytes-like object or ASCII string s and return the decoded bytes .
Optional casefold is a flag specifying whether a lowercase alphabet is acceptable as input. For security purposes, the default is False .
RFC 4648 allows for optional mapping of the digit 0 (zero) to the letter O (oh), and for optional mapping of the digit 1 (one) to either the letter I (eye) or letter L (el). The optional argument map01 when not None , specifies which letter the digit 1 should be mapped to (when map01 is not None , the digit 0 is always mapped to the letter O). For security purposes the default is None , so that 0 and 1 are not allowed in the input.
A binascii.Error is raised if s is incorrectly padded or if there are non-alphabet characters present in the input.
Similar to b32encode() but uses the Extended Hex Alphabet, as defined in RFC 4648.
Similar to b32decode() but uses the Extended Hex Alphabet, as defined in RFC 4648.
This version does not allow the digit 0 (zero) to the letter O (oh) and digit 1 (one) to either the letter I (eye) or letter L (el) mappings, all these characters are included in the Extended Hex Alphabet and are not interchangeable.
Encode the bytes-like object s using Base16 and return the encoded bytes .
base64. b16decode ( s , casefold = False ) ¶
Decode the Base16 encoded bytes-like object or ASCII string s and return the decoded bytes .
Optional casefold is a flag specifying whether a lowercase alphabet is acceptable as input. For security purposes, the default is False .
A binascii.Error is raised if s is incorrectly padded or if there are non-alphabet characters present in the input.
base64. a85encode ( b , * , foldspaces = False , wrapcol = 0 , pad = False , adobe = False ) ¶
Encode the bytes-like object b using Ascii85 and return the encoded bytes .
foldspaces is an optional flag that uses the special short sequence ‘y’ instead of 4 consecutive spaces (ASCII 0x20) as supported by ‘btoa’. This feature is not supported by the “standard” Ascii85 encoding.
wrapcol controls whether the output should have newline ( b’\n’ ) characters added to it. If this is non-zero, each output line will be at most this many characters long.
pad controls whether the input is padded to a multiple of 4 before encoding. Note that the btoa implementation always pads.
adobe controls whether the encoded byte sequence is framed with , which is used by the Adobe implementation.
Decode the Ascii85 encoded bytes-like object or ASCII string b and return the decoded bytes .
foldspaces is a flag that specifies whether the ‘y’ short sequence should be accepted as shorthand for 4 consecutive spaces (ASCII 0x20). This feature is not supported by the “standard” Ascii85 encoding.
adobe controls whether the input sequence is in Adobe Ascii85 format (i.e. is framed with ).
ignorechars should be a bytes-like object or ASCII string containing characters to ignore from the input. This should only contain whitespace characters, and by default contains all whitespace characters in ASCII.
Encode the bytes-like object b using base85 (as used in e.g. git-style binary diffs) and return the encoded bytes .
If pad is true, the input is padded with b’\0′ so its length is a multiple of 4 bytes before encoding.
Decode the base85-encoded bytes-like object or ASCII string b and return the decoded bytes . Padding is implicitly removed, if necessary.
base64. decode ( input , output ) ¶
Decode the contents of the binary input file and write the resulting binary data to the output file. input and output must be file objects . input will be read until input.readline() returns an empty bytes object.
Decode the bytes-like object s, which must contain one or more lines of base64 encoded data, and return the decoded bytes .
Encode the contents of the binary input file and write the resulting base64 encoded data to the output file. input and output must be file objects . input will be read until input.read() returns an empty bytes object. encode() inserts a newline character ( b’\n’ ) after every 76 bytes of the output, as well as ensuring that the output always ends with a newline, as per RFC 2045 (MIME).
Encode the bytes-like object s, which can contain arbitrary binary data, and return bytes containing the base64-encoded data, with newlines ( b’\n’ ) inserted after every 76 bytes of output, and ensuring that there is a trailing newline, as per RFC 2045 (MIME).
An example usage of the module:
>>> import base64 >>> encoded = base64.b64encode(b'data to be encoded') >>> encoded b'ZGF0YSB0byBiZSBlbmNvZGVk' >>> data = base64.b64decode(encoded) >>> data b'data to be encoded'
Security Considerations¶
A new security considerations section was added to RFC 4648 (section 12); it’s recommended to review the security section for any code deployed to production.
Support module containing ASCII-to-binary and binary-to-ASCII conversions.
RFC 1521 — MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies
Section 5.2, “Base64 Content-Transfer-Encoding,” provides the definition of the base64 encoding.