Import from the format you already export — or a screenshot — and get a practice plan built from your own shot data.
What you have
4,812 rows.
Ball speed, launch, spin, carry, side. A folder of CSVs going back two winters. Every number you could want about what already happened.
What you don’t
One sentence about Thursday.
Which numbers matter and which are noise. What the last session says about the next one. Whether any of this is going to show up on a scorecard in April.
Nine formats, auto-detected from the file itself. You don’t pick your device from a dropdown — you upload the export and it works out what it is.
Rapsodo
MLM2PRO CSV export
Garmin
Approach R-series JSON export
TrackMan
TPS session CSV
FlightScope
Mevo and Mevo+ stats CSV
SkyTrak
SkyTrak / SkyGolf CSV
Foresight
FSX, GC3, GCQuad, Launch Pro
GSPro
Simulator session export
Awesome Golf
Session CSV export
Generic CSV
Anything else with sane column headers
And when the export is awkward: hand it a screenshot of the session summary instead and it will read the stats off the image. Nobody should be retyping forty rows into a form.
Brand names are used to identify file formats we read. GolfSalt has no partnership with, and no endorsement from, any launch monitor manufacturer, and we make no claims about how accurate any device’s numbers are. We read what your device gives you.
When the shots come in they become a practice session with a shape: what you were working on, what the dispersion actually says, and how it compares to the last time you hit the same club.
You can attach video to individual shots, and the coach reads the session against your rounds — because a tight 8-iron on a mat means something different if your scorecard says you’re losing strokes with the driver.
Session read — 62 shots, 8-iron and PW
Your 8-iron is fine. Carry is within three yards of your November average and the spread is tighter. Nothing to do here.
The pitching wedge is the story. Full swings carry 118. Your 8-iron carries 152. There is a 34-yard step between two consecutive clubs, and half your approach shots last season started in that window.
Next session. Three-quarter wedges at two set numbers, logged, so we find out whether you own that gap or need to talk about the set.
Illustrative example. Yours is written from your own shots.
The number becomes an instruction. That’s the whole product in one step.
Finish the session and export as you already do. Or screenshot the summary.
Upload it. The format is detected, units normalised, junk shots flagged.
Get the session analysis — what changed, what held, what it means for your rounds.
Your practice plan updates with the next session's work, and the reason it's there.
You have five months, a bay, and no scorecard to hide behind. Most of that time gets spent hitting drivers at a screen and arrives in April as nothing. The difference between winter work that transfers and winter work that doesn’t is whether it was aimed at something your rounds actually exposed.
November
Last season’s rounds go in. The coach names the two or three things that actually cost you strokes, and the winter has a subject.
December – March
Every session imports and gets read. The plan moves as the numbers move, and the record accumulates instead of scrolling away.
April
First real round back gets analysed against all of it. You find out what held outdoors — which is the only test that ever counted.
The question that has no good answer inside a launch monitor app:
I'd like your thoughts on this set of data from a few 8-irons yesterday. I've lost 10-20 yards on my irons these past couple of weeks and can't figure out why.
A launch monitor owner on MyGolfSpy
Indoor golf stopped being a workaround some time ago.
9M+
simulator players in the US
NGF, 2025
$250–$1,100
already spent per year on simulator software
FT / GolfSimulatorSource, 2026
+58%
year-over-year growth in virtual rounds among Garmin app users
Garmin, 2025
$499–$1,099
entry price range for consumer launch monitors
Manufacturer pricing, 2026
“My launch monitor app already has analytics.”
It reports. It doesn't decide what you should do on Thursday, and it can't see your rounds. Those are the two things that turn a session into improvement.
“Will it read my vendor's export?”
Nine formats are read directly and detected automatically, with a generic CSV path behind them and screenshot parsing when an export is awkward. If yours genuinely doesn't fit, tell us — that's a bug worth fixing, not a limitation to argue about.
“Do I have to change how I practise?”
No. Export the way you already export. The change is what happens after — the session gets read, and the next one has a reason.
We read what your device reports. If your unit is placed badly, or the numbers it produces drift from what the ball actually did, we inherit that — we don’t correct it and we won’t pretend to.
Mat work is mat work. Sessions indoors are excellent evidence about gapping, contact and repetition, and weak evidence about lies, wind, and what your hands do on the 16th tee with a card going.
And the coaching gets sharper when round data sits next to the shot data. A launch monitor on its own tells us how you hit it. Your scorecard tells us what it cost.
Straight answers about imports, formats, and what happens after.
Turn it into a decision about your next session. On its own, a launch monitor reports what happened — carry, ball speed, spin, dispersion — but it does not tell you what to work on. GolfSalt imports the session, reads it against your other sessions and your rounds, and writes the next practice plan from what it finds.
GolfSalt reads exports from Rapsodo, Garmin, TrackMan, FlightScope (including Mevo and Mevo+), SkyTrak, Foresight (FSX, GC3, GCQuad, Launch Pro), GSPro and Awesome Golf, plus a generic CSV path for anything else with sensible column headers. The format is auto-detected from the file, so in practice you export and upload. When an export is awkward, you can hand it a screenshot of the session stats instead.
Because reporting and coaching are different jobs. Your vendor's app is very good at showing you the numbers from the session you just hit. It does not know your rounds, your goals, or what you worked on in November, and it does not decide what you should do on Thursday. That decision is what GolfSalt is for.
By practising against a question rather than a number. Sessions that chase peak ball speed tend not to survive contact with a real course. GolfSalt sets the winter work against the gaps your rounds exposed last season — the carry numbers you actually need, the club that keeps costing you strokes — and keeps a record so that in April you can see what held and what did not.
Yes. Simulator session exports import the same way as range sessions, and GSPro and Awesome Golf formats are read directly. Simulator rounds are practice data rather than course data, and the coaching treats them that way — useful for gapping and repetition, weaker evidence about how you'll play under pressure outdoors.
Related pages, if this is only half your situation.
Upload the export you already have and read what comes back. That's the whole trial.
© 2026 GolfSaltAI. Your AI-powered golf coach.