PrintaView is a standalone Windows desktop app for browsing and previewing files from your Downloads folder in one unified view (including all sub-folders).
Main application view with and without the details pane
Right-click context menu with hide and favourite actions
The four settings tabs
Refresh these screenshots from the bundled sample images in images/staging/ with:
npm run screenshotsTo use a different demo folder, pass its path:
npm run screenshots -- "path/to/PrintaView Demo Images"- Recursive browsing of a selected root folder, defaulting to
Downloadsand allowing quick folder changes. - Preview-first browsing for common file types, including images (
png,jpg,jpeg,bmp,gif,webp,tif,tiff,ico,psd) andpdf. - Fast thumbnail generation for images and PDF cover pages, with page counts for multi-page PDFs.
- Generic preview tiles for supported non-image file types such as
docxandpptx. - Search and filtering by file type, favourites, modification date, and file size.
- Sort options for
Newest,Oldest,Name, andType, with type-grouped browsing. - Favourites workflow with a simple
All/Favouritestoggle and per-item favourite actions. - Hidden file management that stays inside the app instead of changing the Windows hidden attribute; includes
Show Hidden Files, per-item unhide, and clear-all support. - Duplicate review that compares matching files side by side and lets you preview, open, reveal, or delete them.
- Optional details pane with metadata, adjustable preview size, and configurable left/right placement.
- Keyboard and mouse-friendly actions for opening files, revealing them in Explorer, and moving them to the Recycle Bin.
- Settings for theme selection (
Default,Pastel Pink,Baby Blue), default file type filters, custom extensions, and per-user app preferences.
- Install dependencies:
npm install- Run the app:
npm start- Run tests (Electron UI tests are headless by default):
npm run test:allTo show the app windows while debugging UI tests, set PRINTAVIEW_TEST_HEADED=1 before running npm run test:e2e or npm run test:packaged.
npm run build:winBuild output is written to the release folder as a portable executable that can be run from anywhere.
After the Test on Main workflow succeeds, semantic-release analyses commits on main. When they require a release, it automatically updates the package version, creates a vX.Y.Z tag and a GitHub release titled PrintaView vX.Y.Z, then builds an unsigned MSIX and portable EXE. The portable EXE is attached to the GitHub release, while the MSIX is submitted directly to Microsoft Store and is not published as a release download. The Store signs the package; no signing certificate is needed.
Before the first release:
- Create and reserve the PrintaView product in Partner Center. Set up its Store listing and pricing, then obtain the product identity values.
- In the GitHub repository, add these Actions variables using the values from Partner Center's Product identity page:
MSIX_IDENTITY_NAMEMSIX_PUBLISHERMSIX_PUBLISHER_DISPLAY_NAME
- Add these Actions secrets for the Microsoft Store CLI service principal and product:
STORE_IDTENANT_IDSELLER_IDCLIENT_IDSECRET_VALUE(the service principal client secret)
- Ensure the service principal has permission to manage the PrintaView product in Partner Center.
The workflow commits the calculated version to package.json and package-lock.json. The MSIX version is derived from that release version and converted to the four-part format required by Windows.
To build the unsigned package locally after installing dependencies:
npm run build:win
npx electron-builder --win dir
.github\scripts\package-msix.ps1 -Version (node -p "require('./package.json').version")Set the three MSIX_* environment variables to the Partner Center identity values when producing a package intended for Store submission.
Releases are driven by Conventional Commits merged to main:
fix: ...creates a patch release (for example,1.0.5→1.0.6).feat: ...creates a minor release (for example,1.0.5→1.1.0).- Add
!after the type or includeBREAKING CHANGE:in the commit body to create a major release. - Other commit types that do not indicate a feature, fix, or breaking change do not trigger a release.
Pull request titles and commit messages are checked for Conventional Commit formatting. Use a release-triggering title such as fix: correct PDF preview or feat: add folder filtering when the change should ship. When CI succeeds on main, semantic-release updates package.json and package-lock.json, creates the version tag and GitHub release, and triggers the Windows packaging and Store submission job. The GitHub release includes the portable EXE; the unsigned MSIX is submitted directly to Microsoft Store only. No manual version bump or tag is needed. See .github/workflows/conventional-commits.yml, .github/workflows/release.yml, and .releaserc.json.






