Glowforge Interface - How to Align a Double Sided Engrave 🤔

Just thought I would link this discussion to another problem that I was testing for @jtbarrett.

Exporting an SVG from Illustrator gave me a file that the GFUI would not process. But using Save As did give me a usable file.

It’s interesting that Illustrator seems to be relying on that assumption as well when the user opens a file that was saved as. Presumably a 1 x 1" artboard would have…
width=“72px” height=“72px"
in it, but what would it spit out if you set your artboard to 1.0069 x 1.0069” (slightly less than 1-1/144" square). Would it say “72.5px”? “72.4968px”?


Not entirely. I was pointing out the disconnect between the authoritative “Save As should not be used” with the fact that it’s been used successfully for many thousands of files in the last 9 months of real life use of the GF by many many people. The implication that all those projects did not work, could not work, should not work and all the people using that method (recommended by GF by the way) are doing it wrong because an individual who spelunked the SVGs thinks he has an explanation of why they all can’t be doing what they’re doing flies in the face of reality.

I’m perfectly fine with suggestions, recommendations or observations but pronouncements of absolutes in the absence of all the facts (and since none of us have access to the GF source code, we’re only guessing as to how it’s handling things) is the height of hubris.

Sometimes reality deals theory a sharp smack.


“Should not be used” is quite a bit different than “can not be used”. If @chris1 had said “can not be used” the fact that it actually can be used would be a great retort.


Lol, I was going to say something like “calm down Francis” but you covered it quite well with your TL’dr.

1 Like

Really trying hard to stay up on this amazing topic and important issue. I appreciate your tenacity because it has been enlightening for so many issues. I’m thankful that you are putting this effort into the forum because much good can come of this.

Are we talking about recommended best practices? In the sense that, if we are all starting from scratch with the same learning curve to deal with, export is the better habit to use for making GFUI ready files for several reasons. Save as works but causes a file description that might be more open to problems.

I am think about qwerty keyboards versus colemak keyboards. Anyone with a smidgeon of statistical acumen would be insane to endorse qwerty over colemak or some other letter frequency/home position based layout. And yet, what do we have? The burden of legacy infrastructure and educational/informational pathways. It pained me each year when I taught technology to elementary students. I knew I was teaching them a less efficient method of touch typing, and yet I still did it. It works well enough. Enough that it balanced out the hassle of learning to reconfigure keyboard layouts in software and on the hardware itself and being prepared for the rest of your life to have to roll your own.

There is the ideal and there is the real. I do believe we can agree on best practices, but personal workflows will be personal workflows.

But maybe I have totally missed the point here. Sorry if my narrative has nothing to do with the issue at hand.

1 Like

Our advice remains to use Illustrator’s “Save As” feature exclusively for preparing images. You’re welcome to use other approaches. Should you find a bug, we’ll ask you to see if the bug exists when using the Save As approach. (As with any advice, it’s possible we’ll change this at some point in the future).

Until GF comes out and says “sorry, we were wrong, don’t use the Save As method as we previously told you to, use Export instead despite having also told you before that you shouldn’t use Export”, theirs is the authoritative comment on the subject. This is the objective reality that matters - there are no alternative facts in play. Just who to believe, the authors or the observer.

EDIT: Looks like Dan weighed in with some additional authoritative support :slight_smile:

1 Like

Chris a long way back I had a job that failed to render correctly, and ultimately it was discovered that it was because I had used export rather than save as. Once I switched it worked fine, and we were told to use save as by support… there was a lengthy discussion in early pru days about the differences and why save as was the right thing to use. And every ai project since on Prus has used save as…

1 Like

This is the kind of stuff that we really need a wiki to document.


Dan has mentioned several times in the past not to use the export command as it introduces issues, try searching “Illustrator” and “Save As” or “Export”

1 Like

Might want to check the location of that link.

1 Like

He said it again tonight in response to Chris’s admonition not to use Save As. Said you can do whatever you want but if you have a problem Support may ask you to try again using Save As.

I understand. I am referring to the location of the link.

simmah-dah-nah I edited the post :slight_smile:


here is the post:


In my opinion, thank you both for the additional data point. In my opinion, this appears to be the same issue as jbpa had. In my opinion, re-exporting this with the version of Illustrator I have installed produces a working file. In my opinion, I have learned a valuable lesson from this whole experience and in my opinion it would be better for me to not offer advice and assistance going forward. I enjoyed my brief time on the forum and I wish you all the best.


My post was in no way a response to nor a critique of your viewpoint on this matter!

I was simply helping out with locating a post someone else had requested.

I value your contributions and hope you continue to contribute to this forum!

Yep, if Glowforge is coding based on “save as” then in this context, it’s case closed until GF says otherwise.