Alberto Misrachi added a comment - 27/Jul/2023 11:29 PM Still the same? I add some   h3  {     font-size: 20px;     margin: 21px 0 4px 0; } To PDF stylesheet but it does nothing my h3 still shows like 8px

Steven Bao added a comment - 21/Jun/2023 6:34 PM With the new PDF export pages now render more accurately match Confluence pages and you should no longer see this issue:  https://community.atlassian.com/t5/Confluence-discussions/Exported-PDFs-now-more-accurately-match-Confluence-pages/td-p/2130971 However, if you are using @page tags this will fall back to the old legacy PDF export and you may experience this bug. We will be closing this bug, but watch this ticket for @page support in new PDF export:  https://jira.atlassian.com/browse/CONFCLOUD-75975

Oksana Bodnar (Inactive) added a comment - 24/Nov/2022 10:07 AM This is Oksana, I was able to reproduce this bug on November 24, 2022.

Micheal Planck added a comment - 28/Jul/2022 1:49 AM - edited After much research, I have found a work-around. It is not the work-around, because it is impossible to make your PDF look like your web page. However, it produces a PDF that is at least legible. Their are two fundamental problems: 1) the CSS property h1 only sort of applies to the h1 text in your PDF. The .wiki-content h1 also applies, and Confluence has established stupid defaults for each of the 9 wiki heading styles - defaults that conflict with the web page styles. You must override every attribute with the .wiki-content to control what your PDF headings look like. 2) When exporting to PDF, Confluence stupidly demotes all headings by page heiarchy. This means that your h1 (or .wiki-content h1) style appears exactly once: as the title of your home page. All other pages are h2. Their child pages are h3, and if those pages have children, they are h4, and so on. On top of that, all of the styles on your page will also be demoted the same amount as the page. This means that if you have a page with text in h1 style, and it has a child with text in h1 style, your first page will display its text in h2 and your child page will display its text in h3. Therefore, it does you no good to match your .wiki-content heading styles to the web page styles (specifically, the fact that h6 is display: block), because what text is classified as h6 depends on what page it is on. This particular bit of genius should have resulted in an automatic sacking for someone, as it demonstrates that Atlassian simply does not understand the concepts of formatting, exporting, or reading documents. The best you can do is to redefine the styles to at least not be actively dishonest. Then restrict yourself to no more than 5 heading styles and three pages of depth. You must also surrender any desire to control what your document looks like and accept bare legibility instead, but you already know this because you are using Confluence.     /* Put a page break before each page */ /* Note that no other settings can be applied here; trying to set the color */ /* or size will not change the title but will modify text in tables. */ .pagetitle {   page- break -before: always; } /* Add a page number (note this requires <span id= "pageNum" /> in the Footer description)*/ #pageNum:before { content: counter(page); } /* Correct heading font sizes because the default is broken. */ /* Note that H1 appears exactly once, as the Home page title. */ /* All other pages are demoted one level to H2, and any of their children will be H3, etc.. */ /* Any headings on those pages are demoted the same amount as the page. */ /* Thus, if you have 8 levels of child pages, you page name will be in H9 and */ /* all of your text headings will be demoted to an unknown style. */ .wiki-content h1 { color: black; font-weight: normal; font-style: normal; font-size: 26px; } .wiki-content h2 { color: black;   font-weight: normal;   font-style: normal;   font-size: 20px; } .wiki-content h3 { color: black;   font-weight: normal;   font-style: normal;   font-size: 18px; } .wiki-content h4 { color: black;   font-weight: normal;   font-style: normal;   font-size: 16px; } .wiki-content h5 { color: black;   font-weight: normal;   font-style: normal;   font-size: 14px; } .wiki-content h6 { color: black;   font-weight: normal;   font-style: normal;   font-size: 14px; } .wiki-content h7 { color: black;   font-weight: normal;   font-style: normal;   font-size: 14px; } .wiki-content h8 { color: black;   font-weight: normal;   font-style: normal;   font-size: 14px; } .wiki-content h9 { color: black;   font-weight: normal;   font-style: normal;   font-size: 14px; }    

Jason Hullick added a comment - 08/Feb/2022 6:36 AM 💩

Neuromancer added a comment - 08/Nov/2021 9:10 AM - edited This is annoying on a regular basis. H2 is much smaller than H3. How has this not been fixed in a year? It's a core function of Confluence and all they have to do it type in some new numbers for the heading tag font sizes.

Jeff Hoover added a comment - 02/Nov/2021 7:43 PM Additionally, when doing a site export and selecting more than one level of pages, such as one parent page and two child pages, the sizes are messed up in a different way.  Heading3 is larger than all other headings.  There are other issues with Bold and Italic text as well.

Jeff Hoover added a comment - 02/Nov/2021 7:34 PM - edited This is still an issue.  H3 also appears to be bold, so it isn't just 4-6 that are incorrect.

Terry added a comment - 14/Sep/2021 9:51 AM Adding my weight to this. Much of our wiki uses h2/h4 as part of a consistent style. I've played with the PDF page export stylesheet, overriding the styles for those headers, but nothing I do there has any effect.  We can work around by converting some pages to h1/h3 instead, but it's an ugly fix (those headers are too big on screen) and breaks our house style.   

Diego (Inactive) added a comment - 26/Mar/2021 12:44 PM https://community.atlassian.com/t5/Confluence-questions/PDF-Export-Heading-4-is-larger-font-than-Heading-2/qaq-p/1645650