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:

Name:
Email:
Message:

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:

Password Txt Github Hot [exclusive] [OFFICIAL]

This accidental leakage has created a strange voyeuristic entertainment. "Doxing" and data mining have become spectator sports. Communities form around analyzing these leaks—not to steal, but to curate. Users on forums discuss the "quality" of a leak the way a sommelier discusses wine. "This password.txt is from 2016; the quality is low," or "This dump has high hits for gaming accounts."

In early 2025, a surge of commits containing password.txt appeared across dozens of unrelated projects. Security researchers labeled it a because:

Developers often use temporary text files—frequently named password.txt config.json

GitHub allows users to search public code using specific syntax attributes. Security researchers—and malicious actors—routinely abuse these features to find exposed secrets. Common Search Patterns (GitHub Dorks) password txt github hot

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.

Use GitHub Actions Secrets, HashiCorp Vault, or AWS Secrets Manager. 4. Use Tools to Scan Before Pushing

Catch secrets before they ever leave your computer. Tools like or Talisman install local hooks into your Git workflow. They automatically scan your staging area every time you run git commit . If they detect high-entropy strings or files resembling a password.txt , they block the commit from finishing until you review it. 3. Leverage GitHub Secret Scanning This accidental leakage has created a strange voyeuristic

They help developers build common-password dictionaries to block users from choosing weak credentials like 123456 or password .

Imagine this: you're a developer, and you want a quick way to transfer a password from your work computer to your home machine. You create a file named password.txt , paste the credentials inside, push it to a GitHub repository, and make a mental note to delete it later. Now, imagine that instead of you, the person doing this is a contractor for the —and the repository is public. In May 2026, that's exactly what happened, exposing sensitive AWS GovCloud credentials and internal files to the world.

For educational purposes or learning about how not to store passwords, you might find some open-source projects or examples on GitHub that demonstrate insecure practices. However, always prioritize learning from resources that promote secure coding and storage practices. Users on forums discuss the "quality" of a

Storing secrets in the system environment rather than the source code. Pre-commit Hooks: Using tools like git-secrets TruffleHog

: Pertaining to trending security vulnerabilities, active exploit vectors, or top-starred GitHub security repositories containing massive wordlists of real-world leaked passwords. ⚠️ The Danger of Exposed .txt Files on GitHub

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:


 <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


 <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:


<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:

This accidental leakage has created a strange voyeuristic entertainment. "Doxing" and data mining have become spectator sports. Communities form around analyzing these leaks—not to steal, but to curate. Users on forums discuss the "quality" of a leak the way a sommelier discusses wine. "This password.txt is from 2016; the quality is low," or "This dump has high hits for gaming accounts."

In early 2025, a surge of commits containing password.txt appeared across dozens of unrelated projects. Security researchers labeled it a because:

Developers often use temporary text files—frequently named password.txt config.json

GitHub allows users to search public code using specific syntax attributes. Security researchers—and malicious actors—routinely abuse these features to find exposed secrets. Common Search Patterns (GitHub Dorks)

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.

Use GitHub Actions Secrets, HashiCorp Vault, or AWS Secrets Manager. 4. Use Tools to Scan Before Pushing

Catch secrets before they ever leave your computer. Tools like or Talisman install local hooks into your Git workflow. They automatically scan your staging area every time you run git commit . If they detect high-entropy strings or files resembling a password.txt , they block the commit from finishing until you review it. 3. Leverage GitHub Secret Scanning

They help developers build common-password dictionaries to block users from choosing weak credentials like 123456 or password .

Imagine this: you're a developer, and you want a quick way to transfer a password from your work computer to your home machine. You create a file named password.txt , paste the credentials inside, push it to a GitHub repository, and make a mental note to delete it later. Now, imagine that instead of you, the person doing this is a contractor for the —and the repository is public. In May 2026, that's exactly what happened, exposing sensitive AWS GovCloud credentials and internal files to the world.

For educational purposes or learning about how not to store passwords, you might find some open-source projects or examples on GitHub that demonstrate insecure practices. However, always prioritize learning from resources that promote secure coding and storage practices.

Storing secrets in the system environment rather than the source code. Pre-commit Hooks: Using tools like git-secrets TruffleHog

: Pertaining to trending security vulnerabilities, active exploit vectors, or top-starred GitHub security repositories containing massive wordlists of real-world leaked passwords. ⚠️ The Danger of Exposed .txt Files on GitHub

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.

password txt github hot

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.