We know there's already a huge collection of rocket designs, motor files and flight logs out there. ZenRockets can bring in OpenRocket and RockSim designs, RASP motor files and CSV logs from flight computers. Once imported, rockets and motors remain editable, while flight logs become recorded flights you can inspect and compare.
Most commercial motors are already in the built-in catalog, using data from ThrustCurve.org. If yours is missing or you have your own thrust curve, import a RASP file. For a motor you're already designing, add its static-fire data from the motor editor instead.
Rocket designs#
The Rockets dashboard accepts OpenRocket .ork and RockSim .rkt files through a short wizard:
- Upload — drop the file or browse for it.
- Match motors — when the design carries motors, each one is matched against the catalog. Confirm the match, swap it for a different motor, or exclude it with the row's checkbox; if the file holds multiple motor configurations, pick which one to import.
- Review and save — name the rocket and check the import details: stage and part counts, motor resolution, and a line for anything that needs attention. Unsupported parts are reported by name instead of being silently dropped.
The imported rocket opens in the builder with its converted parts ready to review and edit. Check the result before you prepare a simulation.
OpenRocket (.ork)#
Supported components include nose cones, tubes, transitions, trapezoidal, elliptical and freeform fins, inner tubes and clusters, centering rings, bulkheads, launch hardware, parachutes, streamers and mass components. Supported dimensions, materials, placements, colors and mass overrides are preserved.
RockSim (.rkt)#
RockSim import supports designs with up to three stages and converts:
- nose cones, body tubes, inside tubes and transitions;
- trapezoidal, elliptical and custom freeform fin sets;
- centering rings, bulkheads, engine blocks and tube couplers;
- launch lugs, parachutes and streamers;
- mass objects and shock cords, represented as payload components;
- dimensions, material density, axial and radial placement, RGB colors and known-mass overrides.
Imported motors stay attached to their original motor mounts. If the RockSim file contains several simulation entries, the importer uses the motor setup from the newest one it can read. Multi-stage loadouts are supported, as are evenly spaced clusters with the same motor specification and mount radius.
RockSim tube fins, ring tails and external pods are not currently converted. Recovery devices default to apogee deployment, and RockSim simulation conditions, calculated flight results and alternate historical loadouts are not imported, so review those details before simulating.
Motor files (RASP)#
Open Motors from the main dashboard, select Import, and upload a RASP .eng or .rasp file. If the file contains more than one motor, choose which one you want. Review the motor details and thrust curve, then name and save it.
The file's thrust curve is stored as static-fire data and drives the motor's class, designation and performance figures. RASP files do not describe the motor's internal construction, so ZenRockets creates an estimated case, BATES grain stack and nozzle from the overall dimensions and propellant weight. Treat this as an editable starting point, not the motor's actual internal layout.
Flight logs#
Open Flights from the main dashboard and select Import Flight to upload a CSV from your flight computer. Map the available sensor channels, review the reconstructed trajectory and detected events, then save it as a recorded flight. The imported flight opens with its trajectory and charts and can be compared with simulations. Flight Data Import covers the complete process.