XOR Brute Force

XOR Brute Force: Enumerate all possible XOR solutions.

Free · No sign-up required

Text input

Your result is ready to copy or download after running.

Tool options

About XOR Brute Force

Enumerate all possible XOR solutions. Current maximum key length is 2 due to browser performance. Optionally enter a string that you expect to find in the plaintext to filter results (crib).

Input: binary bytes (text input uses UTF-8; a file retains its original bytes). Output: text.

Format reference: XOR Brute Force background and specification

Example

Use “Try example” to load this public sample and its settings, then run it.

Settings used in this example
ParameterExample valueInput and choices
Key length1Minimum: 1. Maximum: 2. Integer
Sample length100Number
Sample offset0Number
SchemeStandardStandard, Input differential, Output differential
Null preservingfalseOn or off
Print keytrueOn or off
Output as hexfalseOn or off
Crib (known plaintext string)""Escape sequences such as \n, \r and \t are supported

Sample keys and passwords are public. Never use them to protect real data.

Input

Sample file · 5 bytes

Download the sample

Result

The example demonstrates the configured operation. Generated values, timestamps or formatting may vary between runs.

Parameters

ParameterDefault valueInput and choices
Key length1Minimum: 1. Maximum: 2. Integer
Sample length100Number
Sample offset0Number
SchemeStandardStandard, Input differential, Output differential
Null preservingfalseOn or off
Print keytrueOn or off
Output as hexfalseOn or off
Crib (known plaintext string)""Escape sequences such as \n, \r and \t are supported

Before interpreting the result

Use the exact key encoding, mode, padding and IV expected by the source system. Historical ciphers are useful for learning and analysis. Encoding alone provides no confidentiality.

How to use this page

  1. Paste your input or open a local file.
  2. Adjust tool options if needed, then choose Run tool.
  3. Copy the result or download the original output bytes.

Inputs and results are not added to the public catalogue or saved in the URL. Processing happens in your browser; HTTP Request and DNS over HTTPS send the requests you explicitly run. Files up to 128 MiB can be opened; decompression and image tools may have smaller processing limits. Large results have a shortened preview. Text and HTML downloads use UTF-8; binary downloads preserve output bytes. Pasted text follows browser newline handling; open a file when exact input bytes matter.

Related tools

Browse encryption / encoding tools