Wireframe (OFM) vs Expanded (EXP/DST) in DesignShop V10: Stop Losing Editability, Colors, and Profit on Every “Save As”

If you have ever opened a customer-supplied embroidery design, hit "Start," and watched in horror as your machine shredded a perfectly good polo shirt, you know the specific flavor of panic that defines our industry. You might ask, "Why can't I change the density?" or "Why did the color palette turn into a clown show?"

After twenty years on the production floor, I have learned that embroidery is an empirical science. It is about physicstension, friction, and penetration. But most production headaches start long before the needle dropsthey begin with the file type.

In the Melco DesignShop V10 ecosystem (and frankly, in all professional digitizing), there is a fundamental truth that saves shops thousands of dollars in wasted inventory: there are essentially only two kinds of embroidery informationWireframe (object-based) and Expanded (stitch-based).

Think of it this way: Wireframe is the architect's blueprint (you can move walls), while Expanded is a photograph of the house (you can stare at it, but you can't move the door without ruining the image). Once you grasp this, you will stop accidentally stripping the intelligence out of your designs.

The calm-before-the-storm truth about DesignShop V10 embroidery file types (youre not doing it wrong)

When a design wont edit, it feels like the software is gaslighting you. You try to lower the density because youre stitching on a thin performance piqué, but the software refuses. The reality is simple: the file likely lacks the "DNA" required to make that change.

In the source video, the host showcases a design of approximately 19,342 stitches. To a novice, a stitch is a stitch. But to a master, that same visual file behaves completely differently depending on whether it carries Wireframe or Expanded data.

If you operate high-performance equipment like melco embroidery machines, this distinction is the difference between a 15-minute seamless run and an hour of thread breaks. Your workflow must bridge two worlds: the fluid editing environment on your PC and the rigid instruction set requested by the machine.

Wireframe (OFM) is objects with brains: why density, angles, and shapes stay editable

In DesignShop V10, Wireframe is synonymous with the OFM format. The core concept is that Wireframe is not a list of needle drops; it is a collection of mathematical shapes + physical properties.

In the Project View, you can see the "skeleton" of the design. The tree reveals exactly how the design was constructed:

• Walk Normal Stitch: Not just a line, but a path with a defined stride length.
• Complex Fill: A defined area filled with a specific pattern.

When you select a Wireframe object (like the pear shape in the tutorial), you expose its "brain." You gain access to critical levers:

• Density: Often set to 4.0 points (approx. 0.4mm spacing). Pro Tip: For standard cotton, 4.0 is a "sweet spot." For thick fleece, you might tighten this to 3.8; for thin satin, you might open it to 4.5.
• Stitch Angle: Shown as 247. Adjusting this helps avoid "push-pull" distortion on stretchy fabrics.
• Stitch Type: Toggling between Fill and Satin instantly.

This is the power of Wireframe. The software recalculates the thousands of needle penetrations instantly based on these rules.

The drag a node test: the fastest way to prove you have real Wireframe data

Here is the tactile test every digitizer must know. In the video, the host clicks the pear shape, and small squares (nodes) appear on the outline. He grabs one and drags it outwarddistorting the fruit.

When he releases the mouse button, snap. The fill stitches automatically regenerate to fill the new boundary.

This automatic refill is your "pulse check." If the stitches don't update to the new border, you are not working with a Wireframe object; you are working with a static stitch file.

The Hidden Prep that prevents file-type disasters later

Before you invest time editing a design, you must verify the integrity of your material. It is like checking the oil before a long drive.

Prep Checklist (The "Pre-Flight" Inspection):

• Check the Tree: Are the items listed as "Complex Fill/Column" (Wireframe) or just "Manual Stitch"?
• The Node Test: Click a major shape. Do you see editable nodes (squares) or just a bounding box?
• Property Scan: specific density values (e.g., 4.0) visible in the property bar, or is the box greyed out?
• Stitch Count Check: Note the count (e.g., ~19k). If you resize and this number stays exactly the same, stop immediately.
• Consumables Stock: ensure you have the basicsstabilizer (cutaway for knits), temporary spray adhesive, and fresh needles (75/11 is a safe standard).

Warning (Mechanical Safety): Never force a machine to sew a design that has been resized more than 10-20% without stitch recalculation (Wireframe). Shrinking a design by 20% while keeping the same stitch count increases density largely, which can cause needle deflection, bird-nesting, or even shatter the needle, sending metal shards flying. Always wear eye protection.

Expanded (EXP/DST) is stitches without memory: why colors go weird and edits disappear

The host demonstrates saving the design via File > Save As and selecting Melco Expanded File (*.exp).

This is a destructive act. It strips away the "brain" (the shapes and density rules) and leaves only the "coordinates" (X, Y movements). Expanded files are like a GPS log of a trip you already took. You can follow the path again, but you cannot decide to take a shortcut, because the map is gone.

If you are exporting for the embroidery machine, this is correct. If you are saving your only copy of a customer's logo this way, you are walking into a trap.

The color shock: why EXP opens with wrong colors (and why its not a bug)

New users often panic when opening an EXP or DST file because the beautiful green pear is suddenly neon red.

The video explains the "Why": Expanded formats are industrial relics. They generally do not store RGB color palettes. They only store instructions like: "Stitch until command 'STOP', then switch to Needle #2."

If your software defaults Needle #2 to Red, the pear becomes Red. It is not a glitch; it is a lack of data.

Setup Checklist (so your exports match your real-world workflow)

Use this checklist to ensure you don't overwrite your "Master" data with "Production" data.

Setup Checklist (The "Safe Save" Protocol):

• Master File: Always save your editable work as OFM first.
• Production File: Export as EXP (or DST) only for the machine.
• Color Validation: If importing an EXP, check the color sequence against a Printed Run Sheet (PDF) to ensure you thread the machine correctly.
• Naming Convention: Use clear names like Logo_Master.ofm and Logo_Production.exp.

The OFM container trap: I have an OFM doesnt always mean I have Wireframe

This is the most dangerous misconception in DesignShop. An OFM file is a container. It usually holds Wireframe data, but it can just hold Expanded data.

The host proves this by copying the "dumb" Expanded stitches and pasting them into an empty OFM file. Visually, on the screen, the two pears look identical. You might even use the Colorize tool to fix the red pear back to green.

However, the "EXP inside OFM" pear still cannot be reshaped. It is essentially a "Zombie File"it looks alive (correct colors, correct format), but it has no brain (no editability).

The practical fix for wrong colors and no edit controls (what you canand cantrecover)

When things go wrong, follow this diagnostic path.

Symptom 1: "My colors are weird/random."

• Diagnosis: You opened an Expanded file (EXP/DST) which ignores color palettes.
• The Fix: This is cosmetic. Manually re-assign the colors in software using your thread chart, then Save As OFM to lock those choices in for next time.

Symptom 2: "I cannot change density or stitch angles."

• Diagnosis: You are working with Expanded data (Raw Stitches).
• The Reality: You cannot restore the "properties" perfectly. You can apply global filters (like "scale density"), but for true control, you need the original Wireframe file or you must re-digitize the shape.

The Save As menu decoded: OFM vs CND vs EXP/DST vs graphics (what each is really for)

The "Save As" menu is your control center. Here is how an expert categorizes these extensions:

• The Master (Wireframe/OFM): This is your source code. It contains nodes, density settings, color logic, and notes.
• The Legacy (Condensed/CND): An older format that acts like a skeleton. Useful for scaling simple designs (like stock fonts) significantly.
• The Runner (Expanded/EXP, DST, DSZ): Raw machine code. Use these only to feed the machine.
• The Proof (JPG, BMP): Visuals for customer approval. Never try to embroider from a JPEG!

The Why that prevents repeat mistakes: file types are a business decision, not just a software choice

Why does this matter to your bottom line? Because in commercial embroidery, rework is the profit killer.

If you only keep Expanded files, a customer request to "make the logo 10% bigger and slightly less dense for a hoodie" requires you to start from scratch. If you have the Wireframe, it is a 30-second edit.

I recommend a strict "Two-Lane Workflow":

1. The Vault Lane: Always archive the Wireframe OFM. This is your insurance policy.
2. The Floor Lane: Generate fresh Expanded files for the machine as needed.

A decision tree you can actually use: which file should you keep, send, or request?

When a customer emails you a file, or you are preparing for production, use this logic flow to avoid disaster.

Decision Tree (File Strategy):

• Q1: Do you need to edit shape, density, or angles?
  • YES: You must have the Wireframe OFM. If you only have DST/EXP, you must re-digitize.
  • NO: Proceed to Q2.
• Q2: Is this going straight to the machine right now?
  • YES: Export Expanded (EXP/DST).
  • NO: Proceed to Q3.
• Q3: Do you need to save specific thread colors for a re-order?
  • YES: Save as OFM (even if it contains expanded data, OFM remembers the color palette assignments).
  • NO: A standard stitch file is fine.

Shop-floor reality: file discipline wont fix hooping, but it prevents the worst redo cycles

Software is only half the battle. You can have the perfect Wireframe file with optimized density, but if your physical setup is flawed, the result will still be poor.

Many issues labeled as "bad digitizing" are actually stability issues. If your workflow includes melco embroidery hoops, you know that standard plastic hoops can be slippery. They pop open on thick jackets or leave "hoop burn" (shiny crush marks) on delicate performance wear.

If you find yourself constantly fighting to get the fabric taut ("tight like a drum skin" is the rule), consider that your file might be fine, but your tools are fighting you. Upgrading to a machine embroidery hooping station ensures repeatable placement, but the real game-changer for many is the hoop itself.

Warning (Magnet Safety): If you upgrade to magnetic hoops, be aware they use powerful Neodymium magnets. They create a severe pinch hazard (they can smash fingers) and must be kept at least 6 inches away from pacemakers and computerized machine screens.

The upgrade path that feels natural: when tools matter more than one more software trick

Once your file workflow is clean (you are using Wireframe, you are exporting correctly), look at your physical bottlenecks.

• Pain Point: Loading a shirt takes 2 minutes, and it's still crooked.
• Solution: Magnetic frames snap fabric into place in seconds without forcing rings together. Terms like magnetic embroidery hoop are your gateway to understanding how professionals strip time out of the process.
• Pain Point: You are turning away orders of 50+ shirts because your single-needle machine takes too long to change colors.
• Solution: This is the trigger for capacity scaling. Moving to a multi-needle platform (like the melco amaya embroidery machine or similiar 15-needle systems) turns those color changes into split-second automatic movements.

Operation Checklist: the export + archive routine that keeps you profitable

Standardize this routine for every operator. It ensures that the "Thinking" happens at the computer, so only "Running" happens at the machine.

Operation Checklist (Ready to Run):

• Master Save: Was the final edit saved as an OFM?
• Production Export: Did you export the correct EXP/DST for the specific machine you are using?
• Visual Sanity Check: Did you open the production file to ensure no stitches were deleted during export?
• Physical Prep: Is the correct bobbin loaded? (Look for the "1/3 rule"white thread visible in the center 1/3 of the satin column underneath).
• Archive: Save both files to the client folder immediately.

The last thing I want you to remember: Expanded is for running, Wireframe is for owning

The takeaway is simple:

• Wireframe (OFM) is your Intellectual Propertyit allows you to adapt, scale, and fix.
• Expanded (EXP) is your Manufacturing Instructionit tells the machine exactly where to stab the needle.

Master the difference, and you move from being a person who "runs a machine" to a professional who "engineers embroidery." And if your volume is pushing the limits of your current setup, remember that smarter files deserve smarter hardwarewhether that implies an upgrade to the melco emt16x embroidery machine class of equipment or simply better hooping technology to secure your success.

FAQ

• Q: In Melco DesignShop V10, why is Density greyed out and stitch angles cannot be changed on an EXP or DST embroidery file?
  A: The file is Expanded (stitch-based) data, so DesignShop V10 has no object properties to edit.
  • Re-open the original editable Master file in OFM Wireframe if available.
  • Use the drag a node test on a major shape to confirm true Wireframe (nodes appear and the fill regenerates after dragging).
  • If only EXP/DST exists, re-digitize the shape (global scale filters may help, but they will not restore true object controls).
  • Success check: Density (e.g., a value like 4.0) and stitch angle fields are selectable, and stitches re-generate after a node move.
  • If it still fails: Treat the design as raw stitches and stop trying to edit propertiesrequest the Wireframe OFM from the source or rebuild.
• Q: In Melco DesignShop V10, why do EXP or DST embroidery designs open with wrong/random colors compared to the original logo?
  A: Expanded formats usually do not store real RGB palettescolor changes are effectively STOP/change needle commands, so software defaults can look random.
  • Re-assign colors manually using the shops thread chart or run sheet sequence.
  • Save the corrected color assignments as an OFM (so the same file opens consistently next time).
  • Validate the needle order before stitching by comparing the on-screen color sequence to the printed run sheet.
  • Success check: The on-screen color sequence matches the intended needle/threading order for the machine run.
  • If it still fails: Ignore the on-screen color appearance and follow the STOP/needle change sequence for production accuracy.
• Q: In Melco DesignShop V10, how can an OFM embroidery file still behave like an uneditable EXP zombie file with no reshape controls?
  A: OFM is a container, so an OFM can hold Expanded stitches without real Wireframe objects.
  • Open Project View/Tree and check whether items show object types like Complex Fill/Column versus Manual Stitch-style entries.
  • Click a main shape and look for editable nodes (squares) instead of only a bounding box.
  • Perform the node-drag test and watch whether stitches automatically regenerate inside the new boundary.
  • Success check: After dragging a node, the fill re-calculates immediately to match the new outline.
  • If it still fails: Assume Expanded data inside OFM and obtain a true Wireframe source or re-digitize for full control.
• Q: What is the safest Master vs Production save routine in Melco DesignShop V10 to avoid overwriting an editable OFM with an EXP/DST export?
  A: Always save the editable Master as OFM first, then export EXP/DST only as a separate production file.
  • Save the finished edit as Name_Master.ofm before any export.
  • Export the machine file as Name_Production.exp (or DST) and never use it as the only archive.
  • Re-open the exported production file for a quick visual sanity check before sending it to the machine.
  • Success check: Both files exist in the client folder (OFM opens with editable properties; EXP/DST opens as run-ready stitches).
  • If it still fails: Stop the workflow and restore from the last known-good OFM; do not keep editing the production stitch file.
• Q: How do I know embroidery bobbin tension is acceptable using the 1/3 rule on satin columns before running a full job?
  A: Use the 1/3 rule on the underside as a quick pass/fail check before committing to production.
  • Stitch a small test area of satin (or a sample from the same design) on the target fabric + stabilizer.
  • Flip the sample and inspect the underside of the satin column.
  • Adjust only if necessary, and re-test after each change.
  • Success check: On the underside, white bobbin thread is visible in the center 1/3 of the satin column (not flooding the edges).
  • If it still fails: Verify the correct bobbin is loaded and re-check basic setup (needle condition, stabilizer choice) before chasing tension endlessly.
• Q: What is the safety risk of resizing an Expanded EXP/DST embroidery design more than 1020% without stitch recalculation, and what is the safe action?
  A: Resizing more than 1020% without recalculating stitches can spike density and cause needle deflection, bird-nesting, or even needle breakagedo not run it.
  • Stop and confirm whether the design is true Wireframe (so stitches will recalculate correctly when scaled).
  • If the file is Expanded, do not force sew the resized result; request the Wireframe OFM or re-digitize at the correct size.
  • Wear eye protection when testing any questionable file change.
  • Success check: After resizing a Wireframe design, stitch count changes appropriately (and the design visually maintains proper spacing).
  • If it still fails: Revert to the original size and rebuild the design for the new dimensions instead of scaling raw stitches.
• Q: What magnetic hoop safety precautions should be followed when using neodymium magnetic embroidery hoops near pacemakers and fingers?
  A: Magnetic hoops use powerful neodymium magnetstreat them as a pinch hazard and keep them away from pacemakers and sensitive electronics.
  • Keep fingers clear when letting magnets snap together; control the closing motion deliberately.
  • Keep magnetic hoops at least 6 inches away from pacemakers.
  • Keep magnetic hoops away from computerized machine screens and other sensitive devices.
  • Success check: The hoop closes without finger pinches, and the operator can handle frames without sudden uncontrolled snapping.
  • If it still fails: Switch to a safer handling method (two-hand placement and staged closing) or pause use until the team is trained on pinch-risk control.
• Q: When hooping problems like hoop burn or fabric slipping keep happening, what is the step-by-step upgrade path from technique to magnetic hoops to multi-needle capacity?
  A: Fix workflow in layers: optimize setup first, then upgrade hooping tools (magnetic hoops/hooping station) for stability and speed, and only then scale capacity with a multi-needle machine if volume demands it.
  • Level 1 (Technique): Verify stabilizer choice (cutaway for knits), use temporary spray adhesive as needed, and confirm fabric is hooped tight like a drum skin.
  • Level 2 (Tooling): If plastic hoops slip or cause hoop burn, move to magnetic hoops and/or a hooping station for repeatable placement and faster loading.
  • Level 3 (Capacity): If jobs are being turned away due to slow color changes on single-needle workflows, evaluate a multi-needle platform to remove color-change bottlenecks.
  • Success check: Load time drops and registration stays consistent without repeated re-hooping or visible hoop-mark damage.
  • If it still fails: Re-check that the design is being edited in Wireframe (not Expanded), because stable hooping cannot compensate for a density/file-type mismatch.