> For the complete documentation index, see [llms.txt](https://docs.talsec.app/freerasp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talsec.app/freerasp/freerasp/wiki/getting-signing-certificate-hash/result-convert-the-sha-256-hash-to-base64-format.md).

# Result: Convert the SHA-256 Hash to Base64 Format

## Step 1: Convert to Base64

To convert the hash to Base64 form, use an online tool like [Base64 Encode](https://base64.guru/converter/encode/hex):

<figure><img src="https://3557356308-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ2PxZTOjhquOxcxftTrm%2Fuploads%2FWPIC5ZZYKBJGaRWc706p%2Fimage.png?alt=media&amp;token=b2e2985d-b02c-4c1d-9795-8b74a5634af8" alt=""><figcaption><p>Example of Base64 conversion</p></figcaption></figure>

After conversion, you'll receive a final Base64 string like this:

```
iIx/AtYu7TpAu5cma4JdDXio5bayFSi89axnyOCjfFo=
```

<details>

<summary>Alternative approach using a command-line</summary>

This command removes colons from a SHA-256 string, then converts the hexadecimal output to a Base64-encoded binary string for Talsec's configuration.

```sh
echo "88:8C:7F:02:D6:2E:ED:3A:53:BB:9C:A6:6B:82:5C:0D:78:A8:E5:B6:B2:11:28:BC:F5:AC:67:C8:E0:A3:7C:5A" | tr -d ':' | xxd -r -p | base64
```

This command will output the final Base64 string:

`iIx/AtYu7TpAu5cma4JdDXio5bayFSi89axnyOCjfFo=`

</details>

## Step 2: Use resulting string in your Talsec configuration ✅

Your work here is done. Insert it into your Talsec configuration.

*Example of a Talsec freeRASP configuration in Flutter with the resulting string:*

<figure><img src="https://3557356308-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQ2PxZTOjhquOxcxftTrm%2Fuploads%2FVsWV16AEWiQGcYSMCdFw%2Fimage.png?alt=media&amp;token=92bf9bf7-11a0-4de7-8864-16bcefe74e1e" alt=""><figcaption><p>Flutter signingCertHash example</p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.talsec.app/freerasp/freerasp/wiki/getting-signing-certificate-hash/result-convert-the-sha-256-hash-to-base64-format.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
