<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Scotticad Dev on Medium]]></title>
        <description><![CDATA[Stories by Scotticad Dev on Medium]]></description>
        <link>https://medium.com/@scotticad.dev?source=rss-cba79f3384e0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ENxh3v6OifNrD3SW</url>
            <title>Stories by Scotticad Dev on Medium</title>
            <link>https://medium.com/@scotticad.dev?source=rss-cba79f3384e0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:34:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@scotticad.dev/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Keep your 3D designs on your own computer]]></title>
            <link>https://medium.com/@scotticad.dev/keep-your-3d-designs-on-your-own-computer-8e87b33b423f?source=rss-cba79f3384e0------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e87b33b423f</guid>
            <category><![CDATA[3d-printing]]></category>
            <category><![CDATA[cad]]></category>
            <category><![CDATA[free-software]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Scotticad Dev]]></dc:creator>
            <pubDate>Sun, 08 Nov 2026 20:43:42 GMT</pubDate>
            <atom:updated>2026-11-08T20:53:47.345Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve been a maker for most of my life, and hopped on the 3D printing bandwagon with everyone else about a decade ago. I print mostly functional prints, for example brackets, boxes, jigs, and cases. These vary from projects that I do for fun to just fixing things around the house. For a long time those designs lived in a popular web app. It was free, it was convenient, and I never thought about where my work actually was.</p><p>Then one of their updates broke half a dozen of my designs, and I realised I didn’t really own my data. I had a login, and a folder of STL exports. My original data, the careful construction of basic shapes grouped together, resided only in the cloud.</p><p>An STL isn’t your design. It’s the output: a mesh of triangles, ready for the slicer. The design is everything you built it from, the shapes, the sizes, the holes, the way the parts are grouped. That’s the part you edit when the screw hole is half a millimetre too small. If you lose it, you start again from scratch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hk3oR9DSxiJWVEkNBPtYgA.png" /><figcaption>Every link in the chain is something that can break.</figcaption></figure><p>In this post I lay out the case for running a local CAD program and keeping the original on your own disk. Some of these reasons are about risk, some are about everyday convenience, and a few are just about it being your work.</p><h3>1. You own the file</h3><p>A file on your disk is yours in a way an entry in somebody’s database never is. Nobody can revoke it, reprice it or decide you’ve broken a rule. You can copy it, rename it, email it, print it out and frame it. Nobody needs to give you permission.</p><p>For the longest time, this is how we did things. We load up our word processor, we write our letter to grandma, and we save it locally. Why did this need to change?</p><h3>2. Services shut down</h3><p>Start-ups run out of money. Products get bought and folded into something else. Free tools get “sunset” because they never made any money. When it happens, you usually get an email and a deadline to export your work, if you’re lucky. If you miss the email, the deadline passes without you.</p><p>Even if you get the email that the product is going, often times there’s nothing you can do about it because the file is in proprietary cloud storage. If you’re lucky, then maybe they’ll offer you the option to upgrade to a premium product with a monthly subscription where you can still access your data.</p><h3>3. Prices change</h3><p>Free tiers shrink. Limits appear on how many designs you can keep, or how many can be private. A tool you’ve built years of work in can double in price, and by then moving away is expensive. You either pay or start again.</p><p>Subscription software and the cloudification of our data went hand in hand. We never own an application anymore. There’s much more money in it if we can be made to pay monthly.</p><h3>4. Terms change</h3><p>The terms you agreed to when you signed up aren’t always the terms you have now.</p><p>They change, usually with a notice nobody reads, and continuing to use the service counts as accepting them. That includes what the company may do with your uploads, such as using them to train its AI models. Maybe you don’t care if your data is used to train somebody’s AI models, but it’s your data, and it ought to be an opt-in rather than an opt-out.</p><h3>5. Accounts get locked</h3><p>An automated system flags something. A card payment fails. You lose access to the email address you signed up with. Whatever the reason, a locked account locks up every design in it, and you’re at the mercy of a support queue to get them back. These support queues are increasingly known to be staffed by machines rather than people. Getting a human to answer a support issue on cloud-based software can be almost impossible. You have nobody to explain your situation to. You have nobody who can get you the access to your data back.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Puc3ieh_g_xm_4x5CtIBGA.png" /><figcaption>None of these needs you to do anything wrong.</figcaption></figure><h3>6. Privacy</h3><p>You made it. You own it. Why is it on someone else’s server? What are the potential unintended consequences. Some of your work might be private or sensitive. Maybe you’re working on client work, a product you haven’t launched, anything under an NDA, or something that just isn’t anybody else’s business. Even if you’re just designing 3D prints for your own use, it’s nobody’s business but yours. Furthermore, cloud services get hacked all the time.</p><p>A local file goes where you send it and nowhere else.</p><h3>7. It works offline</h3><p>Multiple times I’ve been bit by a service interruption. Sometimes it’s my own broadband Internet provider. Maybe a tree falls on the cable line. My printer is here. My computer is here. My application and files are on the other side of the planet. Maybe the service outage is on the application’s end. In that setting it doesn’t matter if you have a quickie hotspot you can turn on or not. You have to wait for them to restore it from their end.</p><p>Plus there’s all those times when you’re mobile or away from the Internet. Maybe you’re going on vacation and you want to do a little 3D modeling. Personally I like to rent a beach house, and be alone with my work from time to time. You might not have a reliable Internet connection.</p><h3>8. It’s fast</h3><p>With cloud software, the performance often depends on what kind of a day the provider is having. I drag and drop a square in the online CAD program and I get the spinning circle that it’s thinking about. Or I do a union group and the application pauses for five seconds.</p><p>I bought myself a nice computer. I picked the CPU, the RAM, and the GPU I wanted. Why am I boholden to some provider’s choices on how much resources I get to use on their server.</p><h3>9. You choose when to upgrade</h3><p>This comes back to my gripe at the top of the post about how they did an upgrade and suddenly a bunch of my designs were broken. I didn’t ask for the upgrade. I didn’t want the upgrade. There’s no way to go back. My data was unusable.</p><p>A web app updates when its owner decides, for everybody at once. If the new version breaks your designs or drops a feature you relied on, that’s that. With local software you can keep the version that works for you, and upgrade when you’re ready, or never. You can roll back to a trusted version if you have an issue. You can even run multiple versions simultaneously.</p><h3>10. It lasts</h3><p>Will you be able to open today’s design in twenty years? With a file in a plain, readable format, very probably, even if the program that made it is long gone. With a design locked in an online service, that depends entirely on the service still being there.</p><p>If you don’t think about these things now, in the present, then when the future comes there will be nothing you can do about it.</p><h3>11. Plain text works with everything else</h3><p>Now I’m going to talk about file formats. I’m a proponent of storing data in text representation when feasible rather than binary. If your design is a text file, a whole world of ordinary tools works on it. You can keep it in git and see exactly what changed between versions. You can search a folder of designs for every part that uses a 3 mm hole. You can generate variations from a script, or compare two versions side by side.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pJVd4iVPIdrdwqsYAKXrsQ.png" /><figcaption>A design that’s a text file has a history you can read.</figcaption></figure><h3>12. Backups are up to you</h3><p>Backing up sounds like a chore, but it’s actually the point. A cloud service backs up its own servers, on its own terms, for its own reasons. That doesn’t help you if it’s your account that’s gone. With local files, the old rule applies: three copies, on two kinds of storage, one of them somewhere else. A USB drive in a drawer and a sync folder will cover most people.</p><p>This does mean you’re taking on more resposibility, but you get to own that responsibility with tools that you choose and you control.</p><h3>“But the cloud is convenient”</h3><p>Indeed it is. Sharing a link is easier than emailing a file. Working on two computers is easier when everything syncs. And it’s nice when somebody else looks after the backups.</p><p>But you can have most of that without giving up the original. Put your design folder in a sync service you already use, or in a git repository you control. The difference is which copy is the real one. When the file on your disk is the original and the cloud holds a copy, losing the cloud costs you a copy. When the cloud holds the original, losing it costs you the design.</p><p>People have been arguing this for years under the name “local-first” software: your data lives on your device first, and the network is there to help, not to hold your work hostage.</p><p>I’m a big fan of using github. It’s free. It can hold your designs. Plus, you’ll get handy revision history too.</p><h3>Before you trust a tool with your designs</h3><p>Whatever you design in, it’s worth asking these questions before you put years of work into it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lV4ACJLvBjyDxTL_iJXVLg.png" /><figcaption>If the answer to any of these is no, keep your own copy, and check it opens.</figcaption></figure><h3>Why I wrote ScottiCAD</h3><p>Now that I’ve sold you on why local first is important, I’m going to tell you about one of my projects and why I did it. I went looking for a simple CAD program for 3D-printable parts that runs on my own computer and keeps my designs in ordinary files. I didn’t find one I liked, so I madeone myself.</p><p>ScottiCAD is free and open source, and runs on Windows and Linux. There’s no account, no sign-in, and no internet connection needed. Designs are saved as .scotticad files, plain JSON text, in whatever folder you choose, and scripts are plain text too. You can open both in a text editor and you can keep them in git.</p><p>You can find it at <a href="https://scotticad.com/">scotticad.com</a>.</p><p>Whatever you use, keep the original on your own disk.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e87b33b423f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>