Turn your FFMI and body-composition inputs into a clean downloadable report. Preview the data first, choose exactly what to include, then export a presentation-ready PDF or spreadsheet-friendly CSV.
Use a polished report for coaches, clients, check-ins, personal records or a printable snapshot.
Use rows and columns when you want spreadsheet analysis, archiving, filtering or combining multiple check-ins.
Review calculated values, identifiers, notes and included sections before creating either file.
The builder is designed to calculate and generate files in the browser rather than submitting the form to a reporting server.
Enter the measurements you want to record, customize the report, preview it, and export the same data as PDF or CSV.
FFMIPro report
Both files can contain the same measurement, but they solve different problems.
A PDF keeps headings, labels, spacing and branding together in a readable document. Use it when presentation matters more than data manipulation.
A CSV is lightweight structured text. Open it in spreadsheet software, append new rows, filter measurements or build your own progress charts.
Keep a report minimal or include formulas and notes. Removing unnecessary information also makes a shared report easier to read.
The export workflow is implemented in browser-side JavaScript, allowing a report to be built without a form submission to an export endpoint.
Use the same inputs and measurement conditions at future check-ins. Consistency is more valuable than adding excessive precision to a single estimate.
Free-text cells are escaped and formula-like prefixes are neutralized before export to reduce accidental spreadsheet interpretation of user-entered text.
An FFMI calculation is more useful when you can keep it, compare it and understand exactly which measurements produced it. The Export Reports (PDF/CSV) page turns a temporary browser result into a reusable record. Instead of copying numbers into notes by hand, you can enter your body-composition data once, preview the resulting metrics, and create either a polished PDF or structured CSV file.
This matters most when you track progress across multiple check-ins. A number such as “22.4 FFMI” has limited value if you later forget the body-fat estimate, body weight, height, date or measurement conditions behind it. A report keeps those pieces together. For a fresh calculation without exporting, use the FFMI Calculator. For height correction, see the Normalized FFMI Calculator. If you want performance context, the Compare with Elite Athletes page adds published athlete reference data.
Exporting creates a durable snapshot of a measurement session. The most obvious benefit is convenience, but record quality is more important. A complete report can preserve the measurement date, raw inputs, calculated fat-free mass, FFMI, normalized FFMI and contextual notes. Months later, you can reconstruct what happened instead of relying on memory.
Compare repeated reports to see whether increases in body weight are accompanied by higher estimated fat-free mass.
Send one clean PDF instead of screenshots, copied numbers and separate notes.
Store CSV rows in a workbook to organize long-term measurements, dates and calculated metrics.
Exporting does not make an estimate more accurate. It simply preserves the estimate more clearly. Body-fat measurement error still carries into fat-free mass and FFMI, so the report should be treated as documentation of the calculation rather than proof of exact body composition.
Choose PDF when a person will read the file. The format is useful for check-ins, coaching communication, consultation notes, progress folders and printable records because the report keeps a defined layout. Labels stay next to their values, the calculation method can be included, and an optional notes section can explain measurement conditions.
A PDF is also easier to understand when the recipient does not need to manipulate the data. If you are sending one current result to a coach, a branded PDF is usually cleaner than opening a spreadsheet. The exported FFMIPro PDF includes a title, optional name or identifier, the selected measurements, calculated metrics, optional notes, a method summary and a generation footer.
Choose CSV when software will read or reorganize the data. CSV stands for comma-separated values. RFC 4180 documents a commonly used CSV format and the text/csv media type. It describes records on separate lines, optional headers, comma-separated fields and quoting rules for values that contain commas or quotation marks.
That structure is ideal for long-term tracking. A spreadsheet can sort dates, calculate changes, combine multiple reports or create charts. CSV also avoids styling that you may not need when the goal is analysis rather than presentation.
| Need | CSV | |
|---|---|---|
| Readable one-page report | Excellent | Limited |
| Print or share visually | Best choice | Not designed for this |
| Spreadsheet analysis | Awkward | Best choice |
| Combine many check-ins | Manual | Easy to append |
| Preserve layout | Yes | No |
| Lightweight raw data | No | Yes |
The builder separates raw inputs from calculated metrics. That makes the result easier to audit. If an FFMI value looks unusual, you can check the weight, height and body-fat percentage that produced it.
Report title, optional name or identifier, measurement date and optional sex field.
Height, body weight and estimated body-fat percentage in the unit system you entered.
Estimated fat-free mass, standard FFMI and Kouri-style normalized FFMI.
Optional notes plus a concise explanation of the formulas and measurement limitations.
The normalized formula is included as a separate value rather than replacing standard FFMI. That distinction matters when comparing with studies that use other height-adjustment methods.
This page is built around client-side calculations and client-side file generation. The CSV exporter creates a text Blob, generates a temporary object URL and triggers the browser download. MDN documents URL.createObjectURL() as a browser mechanism that returns a blob URL referencing an in-memory object. The PDF exporter uses the jsPDF library loaded in the page and constructs the document in JavaScript.
Local generation does not make a downloaded file anonymous. If you type your name, private notes or other identifiers, those values can appear in the exported file. Remove optional fields you do not want the recipient to receive.
CSV looks simple, but correct escaping matters. Values containing commas, line breaks or quotation marks need to be quoted, and quotation marks inside a quoted field need to be doubled. This page follows those conventional rules and exports UTF-8 text using the text/csv MIME type.
The exporter also treats free-text cells defensively. Text beginning with characters such as =, +, - or @ can be interpreted by some spreadsheet applications as formulas. For user-entered labels and notes, the page neutralizes formula-like prefixes before generating the CSV.
The PDF button reads the same validated report object used by the preview and CSV exporter. It then creates a new jsPDF document, adds the report heading, metadata and selected sections, and saves the finished PDF through the browser. Keeping one source report object reduces the chance that the PDF and CSV contain different calculated values.
If the external PDF library is blocked by an aggressive content blocker or the page is opened without internet access before the script has been cached, the PDF button may not work. The CSV exporter does not depend on that library because modern browsers already provide the Blob and object URL primitives it uses.
For useful trends, standardize the measurement process before worrying about the export format. Measure under broadly similar hydration, food, exercise and time-of-day conditions. Use the same body-fat method when possible. Record notes if a check-in was unusual—for example, after travel, a hard training session or a large meal.
Then compare changes across several measurements rather than treating one decimal place as a biological event. If your FFMI increases gradually while waist, performance and body-fat trends remain appropriate for your goal, the direction may be meaningful. For programming context, pair the report with the Training Volume Calculator. For supplement-related performance planning, see the Beta-Alanine Dosing Guide.
An exported report can look precise while the underlying estimate is not. The largest uncertainty usually comes from body-fat percentage. Consumer BIA scales, calipers, circumference methods, visual estimates, DXA and air-displacement methods do not produce identical values. Hydration and testing conditions can also shift results.
FFMI itself describes fat-free mass relative to height; it does not isolate muscle mass perfectly and does not measure performance. A higher FFMI is not automatically healthier or better for every sport. Use exported reports to improve record keeping and communication—not to turn a body-composition estimate into a medical or anti-doping conclusion.
Educational use only. Exporting does not validate the accuracy of body-fat measurements or turn an FFMI estimate into a clinical assessment. Review all downloaded content before sharing it.
Calculate the numbers, understand the context, then export a record that keeps the inputs and results together.
Calculate standard FFMI from height, weight and estimated body-fat percentage.
Open CalculatorSee how a common height correction changes FFMI interpretation.
Calculate Normalized FFMIAdd published Olympic and collegiate athlete reference context to your FFMI.
Compare ResultsPlan weekly hard-set volume when body-composition progress is tied to resistance training.
Plan VolumeCommon questions about file formats, privacy, spreadsheet compatibility, included fields and the limitations of exported FFMI data.