PDF Printing

Print.js was primarily written to help us print PDF files directly within our apps, without leaving the interface, and no use of embeds. For unique situations where there is no need for users to open or download the PDF files, and instead, they just need to print them.

One scenario where this is useful, for example, is when users request to print reports that are generated on the server side. These reports are sent back as PDF files. There is no need to open these files before printing them. Print.js offers a quick way to print these files within our apps.

PDF files must be served from the same domain as your app is hosted under. Print.js uses iframe to load files before printing them, therefore, it is limited by the Same Origin Policy. This helps preventing Cross-site scripting (XSS) attacks.

Example

Add a button to print a PDF file located on your hosting server:


 <button type="button" onclick="printJS('docs/printjs.pdf')">
    Print PDF
 </button>

Result:

For large files, you can show a message to the user when loading files.


 <button type="button" onclick="printJS({printable:'docs/xx_large_printjs.pdf', type:'pdf', showModal:true})">
    Print PDF with Message
 </button>

Result:

The library supports base64 PDF printing:


 <button type="button" onclick="printJS({printable: base64, type: 'pdf', base64: true})">
    Print PDF with Message
 </button>

Result:

HTML Printing

Sometimes we just want to print selected parts of a HTML page, and that can be tricky. With Print.js, we can easily pass the id of the element that we want to print. The element can be of any tag, as long it has a unique id. The library will try to print it very close to how it looks on screen, and at the same time, it will create a printer friendly format for it.

Example

Add a print button to a HTML form:


 <form method="post" action="#" id="printJS-form">
    ...
 </form>

 <button type="button" onclick="printJS('printJS-form', 'html')">
    Print Form
 </button>

Result:

Print.js accepts an object with arguments. Let's print the form again, but now we will add a header to the page:


 <button type="button" onclick="printJS({ printable: 'printJS-form', type: 'html', header: 'PrintJS - Form Element Selection' })">
    Print Form with Header
 </button>

Result:

W11-x-lite-22621-1992-optimum11-v3-fbconan-.7z -

The Mysterious Archive: Unraveling the Enigma of W11-X-Lite-22621-1992-Optimum11-V3-FBConan-.7z

Target Use: Low-end hardware, older PCs with limited RAM (e.g., 4GB), and gaming setups where maximum performance is prioritized.

The goal of a build like this is simple: Reclaim Resources.

Hash the .7z and any extracted files (SHA-256).
Scan archive with multiple AV engines (VirusTotal or local AV with up-to-date signatures).
Extract in a controlled analysis VM and snapshot before execution.
Inspect scripts/configs for autoinstall actions and network calls.
Boot ISO/WIM in VM, monitor outbound connections, process activity, and created artifacts.
Use static analysis tools to examine binaries (PE headers, signatures) and drivers.
If evidence of compromise, preserve artifacts and isolate networked VMs.

Decoding the Filename

Before we install anything, we need to understand what the metadata in the filename tells us:

Optional Components: Unlike "Ultralight" versions that remove core features, Optimum 11 V3 maintains support for: The Microsoft Store and Xbox gaming. Windows Subsystem for Linux (WSL) and Hyper-V. Additional language packs and fonts.

Stability: Removing core components can sometimes cause issues with specific software or peripheral drivers.

Bottom line

W11-X-Lite-Optimum11 is a fascinating example of Windows “demodding” for performance, but it’s strictly for tech enthusiasts in isolated environments — never for daily drivers or production use. If you’re just curious, search for “FBConan X-Lite review” on YouTube to see it in action without downloading.

JSON Printing

A simple and quick way to print dynamic data or array of javascript objects.

Example

We have the following data set in our javascript code. This would probably come from an AJAX call to a server API:


 someJSONdata = [
    {
       name: 'John Doe',
       email: 'john@doe.com',
       phone: '111-111-1111'
    },
    {
       name: 'Barry Allen',
       email: 'barry@flash.com',
       phone: '222-222-2222'
    },
    {
       name: 'Cool Dude',
       email: 'cool@dude.com',
       phone: '333-333-3333'
    }
 ]

We can pass it to Print.js:


 <button type="button" onclick="printJS({printable: someJSONdata, properties: ['name', 'email', 'phone'], type: 'json'})">
    Print JSON Data
 </button>

Result:

We can style the data grid by passing some custom css: W11-X-Lite-22621-1992-Optimum11-V3-FBConan-.7z


 <button type="button" onclick="printJS({
	    printable: someJSONdata,
	    properties: ['name', 'email', 'phone'],
	    type: 'json',
	    gridHeaderStyle: 'color: red;  border: 2px solid #3971A5;',
	    gridStyle: 'border: 2px solid #3971A5;'
	})">
    Print JSON Data
 </button>

Result:

We can customize the table header text sending an object array Hash the


 <button type="button" onclick="printJS({
	    printable: someJSONdata,
	    properties: [
		{ field: 'name', displayName: 'Full Name'},
		{ field: 'email', displayName: 'E-mail'},
		{ field: 'phone', displayName: 'Phone'}
	    ],
	    type: 'json'
        })">
    Print with custom table header text
 </button>

Result:

JSON, HTML and Image print can receive a raw HTML header: Decoding the Filename Before we install anything, we


<button type="button" onclick="printJS({
		printable: someJSONdata,
		type: 'json',
		properties: ['name', 'email', 'phone'],
		header: '<h3 class="custom-h3">My custom header</h3>',
		style: '.custom-h3 { color: red; }'
	  })">
	Print header raw html
</button>

Result:

The Mysterious Archive: Unraveling the Enigma of W11-X-Lite-22621-1992-Optimum11-V3-FBConan-.7z

Target Use: Low-end hardware, older PCs with limited RAM (e.g., 4GB), and gaming setups where maximum performance is prioritized.

The goal of a build like this is simple: Reclaim Resources.

Hash the .7z and any extracted files (SHA-256).
Scan archive with multiple AV engines (VirusTotal or local AV with up-to-date signatures).
Extract in a controlled analysis VM and snapshot before execution.
Inspect scripts/configs for autoinstall actions and network calls.
Boot ISO/WIM in VM, monitor outbound connections, process activity, and created artifacts.
Use static analysis tools to examine binaries (PE headers, signatures) and drivers.
If evidence of compromise, preserve artifacts and isolate networked VMs.

Decoding the Filename

Before we install anything, we need to understand what the metadata in the filename tells us:

Optional Components: Unlike "Ultralight" versions that remove core features, Optimum 11 V3 maintains support for: The Microsoft Store and Xbox gaming. Windows Subsystem for Linux (WSL) and Hyper-V. Additional language packs and fonts.

Stability: Removing core components can sometimes cause issues with specific software or peripheral drivers.

Bottom line

W11-X-Lite-Optimum11 is a fascinating example of Windows “demodding” for performance, but it’s strictly for tech enthusiasts in isolated environments — never for daily drivers or production use. If you’re just curious, search for “FBConan X-Lite review” on YouTube to see it in action without downloading.

Browser Compatibility

Currently, not all library features are working between browsers. Below are the results of tests done with these major browsers, using their latest versions.

Google Chrome

Safari

Firefox

Edge

Opera

Internet Explorer

PDF

HTML

Images

JSON

Thank you BrowserStack for the support. Amazing cross-browser testing tool.

Development and Support

Please report issues and feature requests in GitHub Issues.

If you have questions when implementing or using the library, ask about it in StackOverflow.

Pull requests are very welcome! Make sure your patches are well tested: README.md.

Print.js was built from the hard work of all these contributors.