Pages and visuals
Page names, layout sizes, visual types, query field references and positions when available.
Turn Power BI project files into a searchable inventory of report pages, visuals, DAX measures, tables, filters, bookmarks and relationships. Then export clear documentation in minutes.
Load a zipped PBIP project or select its report and semantic model folders together.
Or choose an archive, or a folder containing .Report and .SemanticModel files. Folder processing runs locally.
Supported: PBIP project directories, enhanced PBIR, TMDL semantic models, legacy PBIR report.json, model.bim and ZIP archives. A single .pbip pointer file is not sufficient.
Its available metadata and source file will appear here.
All export formats include the metadata actually detected, plus any extraction limitations.
Explore different parts of the project in one place, with source file traceability.
Page names, layout sizes, visual types, query field references and positions when available.
Surface DAX expressions, measure scopes, table names, data types and model columns.
Inspect joins, endpoints, cross-filter direction and active or inactive status.
Find report, page and visual filters, plus saved bookmark definitions and metadata.
Generate a standalone HTML report, editable Word document, Markdown, JSON and CSV extracts.
Search extracted details and locate where each finding came from within the project.
In Power BI Desktop, save your report as a .pbip project. Use the enhanced report (PBIR) format for the richest report-level detail.
Select the entire project folder or ZIP it and select the archive. Include the .Report and .SemanticModel folders if you have both.
Search the metadata explorer, inspect original file paths and create documentation in your preferred format.
Run a self-contained HTML file directly from your computer. No web server, install, CDNs, telemetry or network connection required.
Offline Edition – No Internet Connection RequiredYou are using the self-contained offline edition. Return to the online site when you need a fresh copy of the ZIP or HTML.
Report source files are handled locally via browser File APIs. The app does not upload project contents, execute DAX or M queries, or connect to Power BI services. The online site loads Mightora shared UI and branding, plus live status badge images from GitHub and Shields.io. These badge requests do not include your project files.
The resources below are visible to the browser’s Resource Timing API. This is not a complete network/security monitor.
Resource Timing may omit some requests, including those made by extensions or blocked by privacy settings. F12 may not be available on mobile browsers.
Not currently. PBIX is a packaged binary format and is not parsed by this tool. Save as a Power BI Project (.pbip) and select its entire folder, or create a ZIP of the project. A single .pbip file is only a pointer to the project folders.
Only what can be extracted from the supplied metadata. Semantic model measures and relationships usually require TMDL or model.bim; report details require PBIR or legacy report.json. Some dynamic, binary, encrypted, connected-model or visual-specific properties may be unavailable. This is an inventory, not a full Power BI model validation engine.
No. File reading, metadata parsing and document creation occur entirely in your browser. The online edition loads Mightora shared UI and branding assets; the downloadable offline edition embeds its own assets and blocks network connections with a restrictive Content Security Policy.
No. This version is a read-only documentation and troubleshooting aid. It does not modify report definitions or deploy to Microsoft Fabric.
Markdown suits repository documentation, JSON suits automation, CSV suits inventories, Word suits stakeholder handover, and HTML is a portable read-only report for sharing.
Live evidence from the public GitHub repository. Workflow badges show the latest result for the main branch; they are not independent security certifications.