Repository navigation
locus format
Home > The .locus file
< Previous: Field-aware nodes | Next: Saving & opening >
What Locus Studio stores in a saved design, and why it reopens exactly as you left it.
A Locus design saves to a single, self-contained file. One file holds everything about the design - nothing lives in a sidecar or a separate library you have to keep next to it.
A .locus file stores three things together:
- Your construction: every point, line, circle, arc, region, and boolean you've drawn, exactly as placed.
- Your node graph: the generator side of the design: the nodes and the wires between them.
- The bridge between them: the links that record which node output produced which piece of geometry on the drawing.
Because all three travel together, a saved design is complete on its own. You can move it, back it up, or hand it to another machine, and it reopens as one intact document.
Anything your nodes generate is recomputed when you open the file. The stored result is what you see immediately, but the node graph re-evaluates so the design is live again the moment it loads - ready to adjust, not frozen.
This is why a generated pattern comes back correct even after edits elsewhere in the node graph: the file remembers the recipe, not just the picture.
New designs save with the .locus extension.
Older designs saved as .locus.json still open normally - you don't need to convert them. When you save such a file again, keep whichever name you prefer; both are recognized.
Tip
Treat the .locus file as the master. Exports like SVG or DXF are one-way, flattened snapshots for output - they don't carry your construction or node graph back. Keep the .locus if you'll want to edit the design later. See Exporting SVG and Exporting DXF.
< Previous: Field-aware nodes | Next: Saving & opening >
Found a bug or have feedback? Open an issue | Docs home | Videos | Credits
Getting Started
- Welcome
- How Locus came to be
- Videos
- Community & support
- Installing & launching
- Licensing & activation
- Beta License Agreement
- Core concepts
- Interface tour
- Your first pattern
Modeling - Drawing
- Canvas basics
- Points
- Typing coordinates
- Lines, rays & segments
- Circles & arcs
- Ellipses
- Compass & straightedge
- Rectangles & squares
- Constraining with Shift
Modeling - Editing
- Selecting objects
- Transform tools
- Align & distribute
- Duplicate, detach & ownership
- Regions & booleans
- Cleanup
- Weld & seams
- Style palettes & Re-ink
Annotation
Layers
Modeling Menus
- File
- Edit
- View
-
Draw
- Select
- Point
- Segment
- Line
- Ray
- Circle: Center Point
- Circle: Center Radius
- Circle: Through 3 Points
- Arc: Center, Start, End
- Straightedge
- Compass
- Compass: Radius
- Ellipse: Center + Axes
- Elliptical Arc
- Rectangle: XY-Aligned
- Rectangle: Directed
- Square
- Regular Polygon: Edge
- Regular Polygon: Center, Vertex
- Regular Polygon: Center, Edge Midpoint
- Dimension: Linear
- Dimension: Angle
- Dimension: Radial
- Label
- Construct
- Combine
- Transform
- Select
- Nodes
The Nodes Window
- Basics of visual programming
- How the node graph works
- Sockets & wires
- Adding & connecting nodes
- Sliders & number inputs
- Keeping the node graph tidy
- View menu (Nodes)
- Lists & collections
- Constants & unit conversions
Node Library
- Overview
- Input
-
Primitives
- Point
- Point: Polar
- Segment
- Line
- Ray
- Circle: Center Point
- Circle: Center Radius
- Circle: Apollonius
- Circle Tangent to...
- Circle: 3 Points
- Arc
- Ellipse
- Elliptical Arc
- Rectangle: XY-Aligned
- Rectangle: Directed
- Square
- Regular Polygon: Edge
- Regular Polygon: Center
- Rectangular Grid
- Oblique Grid
- Triangular Grid
- Construct
- Transform
- Image & Fields
- Combine
-
Data
- Measure
- Numbers
- Lists
- Select
- Clean up
- Display
Clusters
Bridging Modeling & Nodes
Patterns & Symmetry
Image-Driven Fields
Saving, Exporting & Files
Preferences & Language
CLI
- CLI server
- locus-cli
- CLI commands
- Tangent circles
- Tick and strike
- Making regions
- Boolean commands
- Reading the node graph
Reference