Thank you! That is what I was missing. The image is still not displaying in the  output:

   <cfoutput>

    The string as an output <br /><br />

    #base64JPG#<br /><br />

    The image as written back to a file<br /><br /><img src="#expandPath("images/newimage.jpg")#" />

    </cfoutput>

But it is writing the file.

Oh right. Just staring at it too long I guess.

Now I have another string. It's a string from a Canvas element. The canvas grabs a signature. I should be able to convert that the same way correct? First I convert it to a base64 string and then to a jpg. It's writing the file again, but I get the same error saying the file is corrupt. Here is how ai am writing this one:

The field with the signature string is called "output"

<!-- Signature Processing -->

<cfset thisString = "#form.output#">

<cfif isdefined("form.output")>

<cfset sig_in_Base64 = toBase64(thisString)>

<cfset sigbase64JPG = sig_in_base64>

<cfset binarySigJPG = toBinary(sigbase64JPG)>

<cffile action="write" file="#expandPath("images/signatures/#form.vin#_Signature.png")#" variable="newSigJPG" output="#binarySigJPG#" addnewline="no" nameconflict="overwrite">

</cfif>

Should this work the same way?

Hmm. again, you would think I would see that.

It did not fix the problem though. It's doing the same as the other script was at the beginning. It writes a file but trying to open it, it says "It may be damaged or use a file format that Preview doesn’t recognize."

It is gathered from an HTML Canvas element in a form (along with some javascript):

<form>

   <div  class="sigPad">

                                        <ul class="sigNav">

                                            <li class="drawIt"><a href="#draw-it" >Your Signature</a></li>

                                            <li class="clearButton"><a href="#clear">Clear</a></li>

                                        </ul>

                                        <div class="sig sigWrapper">

                                            <div class="typed"></div>

                                            <canvas class="pad" width="420" height="55"></canvas>

                                            <input type="hidden" name="output" class="output">

                                                </div>

                                    </div>             

<input type="submit" value="Submit Form" id="submit"  class="button">

                                        <input type="reset" value="Reset Form" class="button" />

</form>

when they submit the form, the value transferred is formatted:

  [{"lx":19,"ly":28,"mx":19,"my":27},{"lx":21,"ly":27,"mx":19,"my":28}, {"lx":25,"ly":27,"mx":21,"my":27},{"lx":30,"ly":27, .......

That is the string that I am trying to convert to the jpg (or png). As an answer to the other question, it does not seem to matter png or jpg. This is where I have it now and I am still receiving the same result:

<!-- Signature Processing -->

<cfif isdefined("form.output")>

<cfset thisString = "#form.output#">

<cfset sig_in_Base64 = toBase64(thisString)>

<cfset sigbase64JPG = sig_in_base64>

<cfset binarySigJPG = toBinary(sigbase64JPG)>

<cffile action="write" file="#expandPath("images/signatures/#form.vin#_Signature.jpg")#" variable="newSigJPG" output="#binarySigJPG#" addnewline="no" nameconflict="overwrite">

</cfif>

Maybe it is not possible to translate it this way? Am I thinking about it the wrong way?

Thanks

That's in the Javascript that is writing the JSON representation of the signature to the hidden field named "output." I am then passing that JSON representation to the server to be processed. Does that make sense?

That is what I was afraid of. Any directions on where I might look?