Clicking "Print" and getting silence back — no error, no paper, nothing — is one of the most frustrating printer problems because there's rarely an obvious clue where to start. This guide breaks the problem down by what's actually failing: the file, the queue, the ink, the connection, or the printer's own settings, so you can go straight to the fix that matches your situation.
Unlike an "offline" message, "won't print" often gives you nothing to go on — the job seems to send, the printer looks ready, and yet nothing happens. That's because a print job can be dropped at several different points without ever surfacing a visible error to the user.
A document you send to print is processed by the spooler, matched against the specific driver for your printer, and only then transmitted for physical output. If the file is corrupted, if the driver misinterprets it, if the queue silently rejects it, or if the printer itself is paused, out of ink, or holding a physical fault like a jam, the job can simply vanish from view with no clear message pointing to why.
Fig. 1 — A print job can be silently lost at the file/app stage, the queue, the driver, or the physical printer itself.
Because "won't print" can originate at the file, the queue, the driver, or the hardware, the list of possible causes is long. These are grouped below by where the fault usually sits.
Fig. 2 — Most "won't print" cases trace back to ink/toner, the queue or driver software, or the file itself.
Many printers block all printing — not just the affected color — once one cartridge is empty or reports critically low, even if you only need black text.
A newly installed cartridge that isn't seated correctly, has its protective tape still on, or isn't recognized due to a chip/region mismatch will block printing entirely until resolved.
A single job that failed partway through often locks the entire queue, meaning every job sent after it — even to a different document — never starts.
The queue can be paused manually or automatically after an error, and stays paused until manually resumed, even after the original problem is fixed.
If a PDF printer, virtual printer, or a second physical device is set as default, jobs can be sent there instead of your intended printer without any warning.
A driver that doesn't match the printer's current firmware version can silently fail to process certain jobs, especially after either the driver or firmware updates independently.
A damaged file, or one saved in a format the printer's driver doesn't fully support, can be accepted into the queue and then quietly dropped instead of printing.
Very large documents, especially high-resolution photos or multi-page PDFs, can exceed the printer's internal memory buffer and fail without a clear error.
Some PDFs are set to block printing at the file level as a security measure; the printer will never process these regardless of driver or connection health.
If a document relies on fonts or embedded elements not available on the printing computer, some drivers substitute blank space rather than throwing a visible error.
Printing directly from a browser depends on the browser's own print engine, which can behave differently from a desktop app's printing and occasionally fails to hand the job off correctly.
When the background spooler service stops responding, jobs can be accepted into the queue but never actually processed for delivery to the printer.
An OS update can silently change a default printer, reset a driver association, or disable a printing-related permission that was previously working.
Some printers refuse every job — without displaying a prominent alert on the computer side — if an ink access door or paper cover isn't fully closed.
A clogged print head can allow a job to be "printed" in the sense that paper feeds through, while producing no visible output at all, which is sometimes mistaken for the printer not printing.
When only certain file types fail to print, the cause is almost always in how that file type is processed rather than in the printer or connection.
Fig. 3 — PDFs, documents, browser pages and photos are each rendered through a different path before reaching the same print queue — which is why one format can fail while others succeed.
PDFs sometimes carry print restrictions set by whoever created the file, use fonts or elements the driver can't fully render, or are simply large enough to overwhelm the printer's memory buffer. Try opening the file in a different PDF viewer and printing from there, and check whether the file is password- or permission-protected.
Missing fonts, embedded images, or tracked changes/comments can occasionally cause a Word document to fail silently. Saving the file as a PDF first and printing that copy is a reliable workaround.
Browser printing depends on the browser's own rendering engine rather than the operating system's printing stack directly. If this fails, try a different browser, or open the page's print preview and save it as a PDF before printing that file instead.
Emails with embedded images, unusual formatting, or web-based content can render inconsistently when printed directly from a webmail client; forwarding the content into a document or using the "print preview" option first usually resolves it.
High-resolution photos are the most likely file type to exceed a printer's buffer, especially over a slower wireless connection. Reducing the resolution or file size before printing, or connecting via USB for large batches, helps.
Multi-page or high-resolution documents can take noticeably longer to spool; give the job extra time before assuming it's failed, and check the printer's available memory setting if this happens often.
If a printer accepts jobs over USB but not wirelessly, the fault is almost always in the wireless connection or driver configuration for that specific connection method — check that the wireless printer entry (not a separate USB entry for the same physical printer) is the one selected as default. If the reverse is true and only USB fails, check the cable, port, and whether the correct USB driver, rather than a generic one, is installed.
Duplex printing relies on a specific hardware unit inside the printer; if that unit isn't installed, is disabled in settings, or the paper type in use isn't supported for double-sided printing, the job can fail or silently default to single-sided.
Non-standard paper sizes and materials need the correct tray and paper-type setting selected in the driver; a mismatch between the physical media loaded and the setting selected is the most common reason these fail while standard paper prints normally.
A ready status only confirms the printer is powered on and connected — it doesn't confirm the current job is being processed correctly. A stuck queue, wrong file interpretation, or driver mismatch can all leave the printer idle and "ready" while your specific job never comes through.
This usually points to an empty, dried, or unrecognized black cartridge, or a clogged nozzle specific to the black ink channel, rather than a driver or connection issue.
A new cartridge that isn't fully seated, still has its protective tape or seal attached, or isn't recognized due to a chip mismatch will block printing until it's correctly installed.
PDFs can carry print restrictions, unusual embedded fonts, or large file sizes that other formats don't, which is why a printer can handle Word documents normally while failing specifically on certain PDFs.
Browser printing uses the browser's own rendering engine rather than the operating system's print stack directly; trying a different browser or printing via a saved PDF isolates whether the browser itself is the problem.
Updates can reset the default printer, break a driver association, or restart print-related services mid-update, any of which can cause jobs to silently fail afterward until the driver is reinstalled.
Yes. A single failed job sitting at the top of the queue commonly blocks every job sent after it until it's manually removed.
This points to the wireless-specific driver entry or network connection rather than the printer itself — check that the wireless printer profile, not a separate USB one, is selected as default.
Large or high-resolution files can exceed the printer's internal memory buffer, especially over a wireless connection, causing the job to silently fail rather than complete.
Duplex depends on a specific internal hardware unit and a matching driver setting; if either is disabled or the loaded paper type isn't supported for duplex, the setting can fail silently or default back to single-sided.
This is usually a separate but related issue — most often a clogged print head or empty cartridge — where the mechanical printing process runs, but no ink or toner is actually deposited on the page.
Non-standard media needs the matching paper-type setting selected in the print driver; using the wrong setting for the loaded media is the most common cause of these specific jobs failing.
This isn't a step to take lightly — some printers are designed to reject or restrict non-official cartridges regardless of quality, so recognition issues are often intentional rather than a fault to work around.
Different applications can use different printing methods (direct system printing versus an app's own print engine), so a fault specific to one method won't necessarily affect the other.
If ink/toner is confirmed full, the queue is clear, the driver is freshly reinstalled, and a simple test file still fails to print on every device that tries, a physical fault such as a clogged print head or internal fault becomes more likely.
Still can't get a page out? Check the related guides above for your specific file type or symptom.
A printer that won't print is rarely a single, obvious fault — it's usually one of a handful of points along the path from file to page quietly failing without an error message. Working through ink and toner status, the print queue, the correct default printer, and the specific file involved covers the overwhelming majority of cases. If the same file fails on every device and every method, that's the point to start suspecting a genuine hardware issue rather than a settings problem.