<doc>

<legacy_id>1652</legacy_id>

<name>base64Decode</name>

<type>function</type>

<syntax>

<example>the base64Decode of <i>encodedData</i></example>

<example>base64Decode(<i>encodedData</i>)</example>

</syntax>

<library></library>

<objects>

</objects>

<synonyms>

</synonyms>

<classification>

</classification>

<references>

<function tag="decompress">decompress Function</function>

<function tag="md5Digest">md5Digest Function</function>

</references>

<history>

<introduced version="1.0">Added.</introduced>

</history>

<platforms>

<mac/>

<windows/>

<linux/>

<ios/>

<android/>

</platforms>

<classes>

<desktop/>

<server/>

<web/>

<mobile/>

</classes>

<security>

</security>

<summary><glossary tag="return">Returns</glossary> the original data from a base 64-<glossary tag="encode">encoded</glossary> <keyword tag="string">string</keyword>.</summary>

<examples>

<example>put base64Decode(receivedData) into URL "file:download.mov"</example>

<example>base64Decode(base64Encode(myData))</example>

</examples>

<description>

<p>Use the <b>base64Decode</b> <control_st tag="function">function</control_st> to take a base 64-<glossary tag="encode">encoded</glossary> <keyword tag="string">string</keyword> and transform it back into the original <glossary tag="binary data">binary data</glossary>.</p><p/><p><b>Parameters:</b></p><p>The <i>encodedData</i> is a <keyword tag="string">string</keyword> of of any length. Valid base 64-<glossary tag="encode">encoded</glossary> data can include uppercase and lowercase letters, digits, +, /, and =. Other characters are ignored.</p><p/><p><b>Value:</b></p><p>The <b>base64Decode</b> <control_st tag="function">function</control_st> <glossary tag="return">returns</glossary> the original <glossary tag="binary data">binary data</glossary>.</p><p/><p><b>Comments:</b></p><p>The <b>base64Decode</b> <control_st tag="function">function</control_st> is the <keyword tag="inverse">inverse</keyword> of the <function tag="base64Encode">base64Encode</function> <control_st tag="function">function</control_st>.</p><p/><p>The decoded result is generally smaller than the encoded data.</p><p/><p>Base 64-encoded data does not necessarily contain any = signs. If a run of one or more = signs is present, it indicates the end of the data.</p><p/><p>The base 64 encoding scheme is often used to encode binary data for MIME mail and HTTP transfers.</p><p/><p>For technical information about base 64 encoding, see section 6.8 of RFC 2045 at &lt;<u>http://www.ietf.org/rfc/rfc2045.txt</u>&gt;.</p>

</description>

</doc>