Redacting a PDF With Rotated or Sideways Pages
A landscape spreadsheet, a sideways scan, an upside-down fax page. Orientation is not a cosmetic detail during redaction — it decides where a black box actually lands and how the finished file is shaped.
Almost every redaction problem covered elsewhere on this site is a question about content: is the text really gone, is there an OCR layer underneath, does the metadata name you, does an uncovered total give away a covered figure. This one is not about content at all. It is about geometry — the shape and orientation of the page itself — and it matters because a redaction box is defined by where it sits on a page, and a rotated page has two different ideas of where anything sits.
The situation is completely ordinary. A litigation exhibit set where the financial schedules were produced in landscape and stapled in among portrait correspondence. A scanned packet where the operator fed three sheets in sideways and never noticed. An architectural drawing bound into a portrait report. A fax-derived page that arrived upside down. In all of these you open the file, the pages look fine on screen, and there is no visible cue that anything unusual is going on underneath. Then you redact, export, and discover that the black bar you carefully placed over an account number on page nine is sitting in an empty margin instead — or that the page you thought was portrait is now reported as landscape by whatever system you are filing into.
This page explains what rotation actually is inside a PDF, why it creates a redaction hazard that ordinary proofreading does not catch, what HidePDF specifically does with rotated pages, and what to check before you send the finished file.
Two different things that both look sideways
The first distinction to get straight is that "this page is sideways" describes two unrelated situations with very different consequences.
A rotation instruction carried by the page. A PDF page can store its content one way up and carry a separate instruction telling every viewer to turn the page by a quarter, half, or three-quarter turn before displaying it. The rotation is restricted to multiples of ninety degrees — that constraint is enforced in practice, and the PDF renderer this site loads rejects any other value outright rather than approximating it. The important consequence is that the content stream is untouched: the text still describes itself in the page's own unturned coordinate system, and only the display step applies the turn. Two coordinate systems now exist for the same page, and they disagree.
A scan that was captured sideways. Here there is usually no rotation instruction at all. The page is an image, and the image itself contains a sideways photograph of a sheet of paper. There is only one coordinate system, and the page is simply a picture of something rotated. Software that reads page properties will report this page as perfectly normal, because as far as the file is concerned it is.
You cannot tell these apart by looking. On screen they produce the same result. The difference shows up in what tools can do about it: a rotation instruction can be changed or removed without touching any pixels, while a sideways scan can only be straightened by re-rendering the image. And, more to the point here, only the first one introduces the coordinate mismatch that misplaces redaction boxes.
Why rotation misplaces a redaction box
Consider a page stored upright but displayed turned a quarter turn clockwise. You see a wide page. You drag a box over a name near what appears to be the top-left. Your box is described in the coordinates of what you saw.
A tool that stores your box as a rectangle and then writes it into the page's own untransformed coordinate space — without applying the same rotation the viewer applied — will place that rectangle somewhere else entirely. Width and height swap roles. What was near the left edge lands near the top or the bottom. The box is still the right size and still perfectly black, so an exported file looks confidently and professionally redacted; it is just covering the wrong region, while the name you meant to hide sits in the open a few inches away.
This is a particularly nasty class of bug because the two most common self-checks both miss it. Reviewing your work in the editor before export shows the box in the right place, because the editor is showing you the display coordinates. And a text-search check on the exported file may come back clean anyway if the export rasterised pages, since the search finds nothing on any page regardless of what is visible. The only check that catches a transposed box is looking at the finished page with your eyes.
The same transposition risk applies to anything else that carries coordinates through the process: extracted text positions, form field rectangles, annotation placements, automatic pattern-matching that reports "found a number at these coordinates". Any workflow that hands coordinates from one step to another has to agree about rotation at every hand-off, and mixed-orientation documents are exactly where such agreements break.
How HidePDF handles rotated pages
The behaviour here is worth stating precisely, because it is the reason the box-misplacement failure above does not apply to this tool.
When a page is displayed, the renderer is asked for that page at its own stored rotation — the default. A page carrying a quarter-turn instruction therefore appears upright and correctly proportioned in the editor, exactly as it would in any normal PDF reader. Your boxes are recorded against that displayed view.
On export, every page is re-rendered the same way, at the same rotation, at a fixed higher resolution, and your boxes are painted onto that rendered image before the page is rebuilt from it. Because the box coordinates and the rendered page come from the same rotated view, they cannot disagree. What you drew is what gets covered. There is no separate coordinate translation step to get wrong.
One structural change does happen, and it is worth knowing about. Each rebuilt page is created at the dimensions of the page as displayed. For a page that was stored upright with a quarter-turn rotation instruction, those displayed dimensions have width and height swapped relative to how the page was stored — so the exported page is a genuinely wide page, with no rotation instruction left to apply. Visually the result is identical. Structurally, the rotation has been normalised away and folded into the page geometry. Mixed-orientation documents survive this fine, because each page is rebuilt at its own displayed size rather than forced to a common one; a file that mixed portrait correspondence with landscape schedules comes out mixed in the same way it went in.
Two things the tool does not do. It has no rotate control — no page rotation, cropping, or reordering of any kind. And it will not straighten a sideways scan, because there is no rotation instruction to act on; a scan captured sideways appears sideways in the editor just as it does everywhere else, and if you want the finished document upright you need to straighten it in another application before redacting. All of this processing happens inside your browser on your own device, with no upload required.
A checklist for a mixed-orientation document
- Page through the whole file before drawing anything. Note which pages are landscape and which are sideways or upside down. Rotation tends to arrive in clusters — a block of scanned sheets fed the same wrong way, or a run of schedules exported from a spreadsheet — so finding one is a reason to look carefully at its neighbours.
- Decide up front whether to straighten first. If pages are genuinely unreadable as displayed, fix orientation in another application before you start redacting rather than squinting through the job. It is much easier to miss sensitive content on a page you are reading at an angle, and the reading step is the part no tool does for you.
- Redact each page in the orientation you can actually read. Resist the temptation to work fast on the awkward pages. Upside-down and sideways pages are where a skimmed read misses a name in a header or a number in a margin.
- Do not resize the browser window part-way through. Boxes are stored relative to the size the page was displayed at, and a resize rescales the boxes you have already placed. On a document whose pages are all the same shape that rescaling is straightforward; on a mixed-orientation document, where pages have different proportions, it is much more fragile. On a phone or tablet this matters more than it sounds, because turning the device is a resize. Pick an orientation, finish the job in it, and if you do resize mid-session, page back through and check every box before exporting.
- Check the landscape and rotated pages first in the exported file. Open the download and look at those pages specifically, before anything else. This is the check that catches a transposed box, and it takes seconds.
- Confirm the finished page shapes are acceptable to the recipient. If you are filing into a system that validates page dimensions, or printing to a fixed paper size, check that a normalised landscape page is handled the way you expect rather than assuming.
Common mistakes and misconceptions
Assuming a page that looks upright is stored upright. It very often is not, and nothing in the viewer tells you. This is harmless with a tool that renders and redacts in the same coordinate space, and the root cause of misplaced boxes with one that does not.
Treating "the box looked right in the editor" as verification. The editor shows the display view. If a transposition happens, it happens during export. Verification means opening the exported file.
Relying on a text search to catch a misplaced box. On a rasterised export, a text search returns nothing on every page whether or not the redaction landed correctly. It is a check that passes for the wrong reason.
Rotating pages in the viewer and expecting it to stick. Many readers let you turn a page on screen for comfort without saving anything to the file. The next person to open it sees the original orientation. If orientation needs to change permanently, that is a deliberate save step in an application that can do it.
Skimming the sideways pages. The most common real-world failure here is not technical at all. Pages that are annoying to read get read less carefully, and redaction is fundamentally a reading task.
Assuming a re-rendered page keeps its original internal structure. An image-based export normalises rotation into the page geometry and replaces text with pixels throughout. That is what makes the covering permanent, but it also means the exported file is no longer searchable or selectable text anywhere, including the parts you kept — decide in advance whether your recipient needs to search it.
Expecting the tool to fix a sideways scan. It will not, and a tool that silently re-oriented your pages would be making a document-altering decision you did not ask for. Straightening is a separate job with a separate tool.
Related guides
Explore more ways to redact PDFs privately, or use the redaction tool above:
Frequently asked questions
Why does one page of my PDF open sideways?
There are two different reasons and they behave differently. A page can carry a rotation instruction in the file that tells every viewer to turn it by 90, 180 or 270 degrees before display, while the underlying content is stored unturned. Or the page can be a scan whose pixels were simply captured sideways, with no rotation instruction at all. The first is a display setting the file carries with it. The second is baked into the image itself. Both look identical on screen, which is why people assume they are the same problem.
Will my redaction box land in the wrong place on a rotated page?
Not in HidePDF. The box is drawn on the page exactly as you see it, and the export re-renders that page at the same rotation before burning the box into it, so the covered region is the region you marked. Misplaced boxes on rotated pages are a known failure in tools that store a redaction as coordinates in the page's unturned coordinate space and then apply them without accounting for rotation, which can send a box to a mirrored or transposed position. If you are using another tool, always open the finished file and look at the rotated pages specifically.
Does HidePDF have a rotate button?
No. The tool does not rotate, crop, reorder or otherwise edit page layout; it draws manual black boxes and rebuilds the file. If a page shows sideways because the file carries a rotation instruction, it will already appear upright and you can work on it directly. If a scan was captured sideways with no rotation instruction, it will appear sideways here as it does everywhere, and you would need to straighten it in another application first if you want the finished document upright.
Does redacting change the orientation of my pages?
Pages keep the orientation you see on screen, but how that orientation is stored can change. HidePDF rebuilds each page at its displayed dimensions, so a page that was stored upright with a 90 degree rotation instruction comes out as a genuinely wide page with no rotation instruction left to apply. Visually nothing moves. A tool that inspects page dimensions, or a print workflow that keys off portrait versus landscape, may report the page differently afterwards, so check before sending files into an automated intake system that validates page size.