Forge Support
Built by a scroller. Supported the same way. Whether it’s a question, a bug, or something that just felt off — there’s a real person on the other end of this page.
Before you reach out — check here first
Most questions come up early, when the workflow is still unfamiliar. These are the ones I hear most often from beta testers.
What does kerf actually mean, and why does RipSaw need it?
RipSaw detected an island. What do I do?
Can I change an entry hole if I picked the wrong spot?
Can I trace over a photo I took myself?
What’s a .forge file? Can I open it in anything else?
.forge file is RipSaw’s native project format. It stores your project data such as shapes, kerf, board boundary, reference image data, bridges, entry holes, and material assignments. It is meant to reopen your work in RipSaw exactly where you left off.My pattern is bigger than one sheet of paper. How does tiling work?
Does RipSaw work on Mac or Linux?
I’m a beta tester — what’s the best way to report something?
Send a message
Whether it’s a bug, a question, or something that just felt off — I want to hear it.
Pick whatever’s comfortable
Some people prefer email. Some prefer Facebook. Either works. This isn’t a corporation — it’s just me at a desk, reading your message.
Best for detailed questions, bug reports, or anything with attachments.
Response Time
I read everything. Usually within a day or two. Longer if sawdust is involved.
Support is part of the build. If something isn’t working, or something could work better — that’s useful. Beta is about finding the edges before they matter.
Less computing. More scrolling.