“Base-encoded data” is one of the patterns that you can select on the Match panel. Use this pattern to match specific bytes or text encoded as base64, base32, or base16. You can also use this pattern to match a certain number of bytes encoded as base64, base32, or base16.

Choose the encoding that the pattern should match.
Choose whether the pattern should Choose if the URL can have an embedded password, as in http://user:password@www.domain.com. URLs can only contain a password if they also contain a user name.
Type in or paste in the sequence of bytes or the text that this field should match according to the encoded data setting.
Bytes are always entered in hexadecimal mode, which is similar to base16 encoding. If you want to enter a base32 or base64 string to be matched literally then you should use the “literal text” pattern instead of the “base encoded” pattern.
Text you enter is internally converted to bytes according to the code page selected via the "encoded data" setting. If you change the code page after entering text then RegexMagic preserves the text and changes the underlying bytes to represent the text using the new code page. You can see the bytes that represent the text by changing "encoded data" to "specific bytes". You can change it from "specific bytes" to a text encoding to interpret those bytes as text according to the selected code page. If you want to interpret them using a different code page, first reselect "specific bytes" and then select the new code page to make sure that RegexMagic preserves the bytes rather than the text.
The length of the base-encoded data matched by this pattern should encode at least this number of bytes.
The length of the base-encoded data matched by this pattern may encode up to this number of bytes.
Do not put an upper limit on the length of the base-encoded data to be matched by this pattern.
Base16 encodes each byte as 2 hexadecimal characters. Hexadecimal editors typically put a space between the bytes and a line break after a certain number of bytes. You can choose whether or not your regular expression should allow whitespace between the bytes. Whitespace includes both horizontal spaces and line breaks.
When the field validation mode is set to “none”, allowing or requiring spacing can allow the field to match more bytes than intended. When allowing spacing, the regex allows 2 or 3 characters per byte and when requiring spacing the regex requires 3 characters per byte. These are assumed to be 2 hexadecimal characters and 1 space but can actually be 3 hexadecimal characters or 3 spaces or any mixture. With all other field validation modes, the field always matches the specified number of bytes and only allows whitespace after every 2 hexadecimal characters.
Base32 and base32hex encode blocks of 5 bytes as 8 characters. Base64 and base64url encode blocks of 3 bytes as 4 characters. When the data to be encoded is not a multiple of 5 or 3 bytes then these encodings pad the output with = signs to make the output length a multiple for 8 or 4 characters. But not all systems that use these encodings require or allow the padding.
Choose whether the letters in base16, base32, or base32hex should be uppercase, lowercase, or case insensitive. Normally these are encoded with uppercase letters. But they are designed to be case insensitive.
This setting does not apply to base64 and base64hex. These encodings are always case sensitive because they use all uppercase letters A to Z and all lowercase letters a to z as part of the encoding.