Building a single post layout with Elementor is the fix for a blog where every article inherits whatever your theme decided years ago: a cramped title, no author box, and a sidebar you cannot move. Elementor’s Theme Builder replaces your theme’s single-post template with one you control, and every published post picks it up automatically. This walkthrough covers the current container-based flow, the widgets that read live post data, and the parts that quietly break.
Quick verdict
Best path overall: Theme Builder > Single Post, laid out with Flexbox containers, published with the condition Include > Posts > All. One template, edited once, applied to the whole blog.
Best free option: there isn’t one. Theme Builder and dynamic tags are Elementor Pro features. Free Elementor can restyle a single post by hand, but it cannot make a template every post inherits.
Skip it if: your theme’s post template is already close and you only want a wider content column or bigger type. A dozen lines of CSS in a child theme is cheaper, faster, and survives a plugin licence lapsing.
Our call: worth doing if you publish regularly and want the author box, related posts, and call-to-action placement under your control rather than your theme author’s. Budget an afternoon for the first template and twenty minutes for every one after that.
What the Theme Builder actually replaces
This is the part most tutorials skip, and it is the reason people get stuck.
WordPress renders a blog post through a template file in your theme. Your theme decides the title size, whether the featured image shows above or below the title, whether there is a sidebar, and where comments land. You do not get a visual editor for any of that.
A Single Post template built in Theme Builder intercepts that. Elementor renders your layout instead of the theme’s file, and pulls the title, featured image, body content, author, and date from the database for whichever post is being viewed. Write a hundred posts, and all hundred use the same template with their own content poured into it.
That distinction matters because a lot of guides, including an older version of this one, tell you to create a page and design a post layout on it. That produces exactly one page. It is not a template, no post will ever use it, and you will spend an hour wondering why.
Before you start
Versions and requirements checked August 2026 against the WordPress.org plugin listing and Elementor’s own documentation.
- Elementor core sits at version 4.2.3 on WordPress.org, with 10+ million active installations, tested up to WordPress 7.1, and needs PHP 7.4 or higher.
- Elementor Pro is required for Theme Builder and for dynamic content. Elementor’s pricing page renders its plan figures in JavaScript and varies them by billing region, so read the Essential renewal rate at checkout rather than trusting a number in any blog post, this one included. Our fuller take lives in the Elementor Pro review.
- Editor V4. Elementor 4.0 introduced the Atomic editor: new elements, design variables, reusable classes, and components. Per the developer update, new installs get Atomic features on by default while existing sites keep their v3 widgets and containers and opt in from Elementor’s settings. If you are updating a live site, nothing moves until you switch it on.
- A staging copy. Publishing a Single Post template changes every post on the site at once. Build it somewhere that is not production.
How to create a single post layout with Elementor
1. Open Theme Builder
In the WordPress dashboard, go to Templates > Theme Builder. It opens as a full-screen app listing the site parts Elementor can take over: Header, Footer, Single Post, Single Page, Archive, Search Results, Error 404, and the WooCommerce parts if you run a shop.
2. Add a Single Post template
Click the plus sign next to Single Post. Elementor’s Single Post documentation confirms this is the site part that pulls dynamic information for whichever post a visitor lands on. Name it something you will recognise in six months. “Single Post 2” helps nobody.
3. Start blank, or borrow a library layout
The template library opens automatically with pre-built single post designs. Inserting one is a reasonable way to see how the pieces fit together on your first attempt: open it, look at what widget sits where, then delete two thirds of it.
By the second template you will be faster starting from blank. Library layouts are designed to look impressive in a screenshot, which usually means an oversized hero image and a typographic scale that fights your existing brand.
4. Build the frame with containers, not sections
Sections and columns are the old structure. Current Elementor builds with Flexbox containers, which nest inside each other, handle alignment natively, and emit less markup. Elementor’s walkthrough for building a template with Flexbox containers covers the mechanics.
A post frame that works, in order:
- An outer boxed container holding everything, with a max width matching the rest of your site.
- A header container: title, post meta, featured image.
- A content container, set narrower than the rest. Long lines of body text are hard to read, and a full-width post body is what makes most custom blog layouts feel unfinished.
- A footer container: author box, share buttons, post navigation, related posts, comments.
If you find yourself reaching for a two or three column structure, you are following a tutorial written for the old editor. Screenshots from that era still rank well, which is most of why this trips people up.
5. Drop in the widgets that read post data
These widgets only make sense inside a theme template, because each one asks WordPress “which post am I on?” and renders accordingly.
Post Title. Set the HTML tag to H1 yourself rather than accepting whatever appears. A template that ships H2 as the largest heading leaves every post without an H1, which is worth understanding properly if you have read our guide to using heading tags in WordPress posts.
Featured Image. Give it a fixed size and aspect ratio. Images without dimensions are named by Google’s Cumulative Layout Shift documentation as a cause of content jumping as the page loads; good CLS is 0.1 or less at the 75th percentile of page loads.
Post Content. The body of the article. Exactly one per template.
Post Info. Author, date, category, comment count, reading time. Add only the meta a reader will actually use.
Author Box. Avatar, name and biography, pulled from whoever wrote the post.
Post Navigation. Previous and next links, so a reader who reaches the end has somewhere to go.
Posts. Related content at the foot of the article. It takes a query, so you can restrict it to the same category.
Post Comments. The comment form and thread, last in the template.
6. Use dynamic tags for everything else
Any control with the dynamic tag icon beside it can be fed from the database instead of typed in. That is how you make a generic widget behave like a post widget: a button whose link comes from a custom field, a heading that prints the excerpt, a container whose background is the featured image.
Custom fields are where this earns its keep. If you store a review score, a recipe time, or a sponsor name per post, a dynamic tag prints it in the layout with no PHP. The awkward part is empty fields, which leave gaps: our notes on hiding a widget when an ACF field is empty cover the fix, and the wider dynamic visibility plugins comparison covers the cases Elementor alone will not handle.
7. Set a preview post before you style anything
In the editor’s bottom panel, open Preview Settings and point the template at a real published post. Designing against placeholder text is how you end up with a template that collapses the first time someone writes a title long enough to wrap onto three lines.
Preview against your longest title and your shortest post. Then preview against a post with no featured image, because you have one, and it will look wrong.
8. Style once, at site level
Set typography and colours in Site Settings rather than on individual widgets. A template styled widget by widget takes an afternoon to rebrand; one built on global fonts and colours takes five minutes. Anything you repeat across templates, such as a newsletter block or a disclosure line, belongs in a global widget.
9. Add sharing with the right widget
Worth stating plainly, because plenty of tutorials get this backwards. The Social Icons widget links visitors to your social profiles. The Share Buttons widget, a Pro widget, lets visitors share your post to their own networks. If you want share buttons on a blog post, Social Icons is the wrong widget.
10. Publish, then set the condition
Hit Publish and Elementor asks where the template applies. For a blog-wide layout: Include > Posts > All. To restrict it, swap Posts > All for Posts > In Category and pick one. Conditions stack, and Elementor’s conditions documentation notes they can include or exclude. Use the exclude side: if a category has its own template, exclude that category from the site-wide one rather than letting both match and hoping the right one wins.
A template saved with no condition displays nowhere. When somebody says their template did nothing, that is usually the whole story.
11. Verify it on real posts
Do not skip this. Open a browser where you are logged out and walk through the list:
- Load three posts of different lengths from different categories. All three should use the new template.
- View source and search for
<h1. There should be exactly one, and it should be the post title. - Load a post with no featured image and check nothing collapses or leaves a coloured gap.
- Check on a phone, not the editor’s mobile preview. They disagree more often than they should.
- Confirm comments render and the form submits.
- Check the ordering of an older post’s headings still makes sense inside the new template, and that your on-page SEO basics survived the move.
What breaks, and how to spot it
The honest section. Every one of these has cost somebody a billable hour.
- Your theme’s post extras vanish. Reading progress bars, custom schema, theme-built related posts, and sticky share rails live in the theme file you just replaced. Elementor does not inherit them. Rebuild them, or accept losing them, but check before you publish rather than after.
- Post Content styling is not fully yours. The Post Content widget outputs whatever the block editor produced. Typography set on the widget cascades down, but block-level colours and spacing set inside the post itself still win.
- Two templates fighting. If posts render inconsistently, open Theme Builder and read every Single Post template’s conditions. Duplicated conditions produce results that look random.
- Comments look wrong. The Post Comments widget renders core WordPress comments and inherits some styling from the theme. If your theme is opinionated, the form may need CSS.
- Weight. Every widget ships its own CSS and JavaScript. A template carrying share buttons, related posts, an author box, and animation is heavier than the plain theme template it replaced. Build the frame, publish, then measure, and treat the WordPress speed guide as the follow-up job rather than an optional extra.
- Lock-in. Deactivate Pro and every post falls back to the theme template. Your content is untouched in the database; your layout is gone. That is a fair trade, but know you are making it.
Which route should you take
- You want a wider column and bigger type. Child theme CSS. Do not install anything.
- You want one consistent post layout with an author box, related posts, and a CTA. Elementor Pro, one Single Post template, condition set to all posts. That is this guide.
- You want different layouts per category. Same flow, one template per category, and exclude those categories from the site-wide template so nothing overlaps.
- You want dynamic layouts driven by custom fields. Elementor Pro plus a custom fields plugin, and expect real setup time.
- You are already fighting Elementor’s weight. Compare alternatives in the page builders roundup before committing your whole blog to one builder’s templates. Migrating out later is a rebuild, not an export.
Once the post template is settled, the same Theme Builder skills carry over: the archive template that lists your posts is covered in our guide to building a blog with Elementor Pro, opt-ins are covered in creating popups with Elementor, and anything Elementor cannot do natively is usually solved by one of the Elementor addons worth installing in 2026.
Frequently Asked Questions
Do I need Elementor Pro to build a single post template?
Yes. Theme Builder and dynamic tags are Pro features. Free Elementor can restyle one post by hand, but it cannot create a template that every post inherits. If you only want to redesign a single article, free is enough. For a blog, Pro is the requirement.
Will my existing posts change automatically?
Yes, as soon as you publish the template with the condition Include, Posts, All. Your writing stays exactly where it is in the database and nothing is rewritten. Only the wrapper around it changes. Delete the template and every post returns to your theme layout.
Can different categories use different single post templates?
Yes. Build a second Single Post template and give it a condition of Include, Posts, In Category, then pick the category. Keep the two mutually exclusive by excluding that category from the site-wide template, rather than relying on which one Elementor picks. Stop at three templates before maintenance eats the benefit.
Why is my template not showing on the front end?
Almost always the conditions. A template saved without one displays nowhere. Open Theme Builder, find the template, and confirm it has Include, Posts, All. Then check that no second Single Post template also matches those posts and is being served instead.
Do sections and columns still work?
Existing section and column layouts keep rendering, but new builds should use Flexbox containers. Containers nest freely, handle alignment natively, and output less markup. Any tutorial that tells you to pick a two or three column structure is describing the old editor rather than the current one.
Does a custom single post template slow the site down?
It can. Every widget loads its own CSS and JavaScript, so a template carrying share buttons, related posts, an author box and animation ships more than a plain theme template did. Build only the frame you need, then measure a real post on a phone before adding extras.
Can I keep my theme comments and schema?
Partly. The Post Comments widget renders core WordPress comments, so those survive. Theme-specific extras such as reading progress bars, custom schema markup or a theme own related posts block live in the template file you are replacing, and need rebuilding in Elementor or adding back with a plugin.
What HTML tag should the post title use?
H1, and set it manually on the Post Title widget. The widget lets you choose the tag, and a template that ships H2 as the largest heading leaves every post without an H1. Check the rendered page source rather than trusting whatever the default happens to be.
The verdict
Build the single post template if you publish often enough that a consistent article layout is worth an afternoon and a Pro licence. The payoff is real: one file controls a thousand posts, the author box and related content sit where you decided, and you stop editing PHP to move a byline.
Do not build it for a site with nine posts and no publishing schedule. Restyle the theme template with CSS, keep the money, and revisit this when the blog is actually earning its place.
If you do build it: containers not sections, conditions set on publish, H1 on the title, and a check on a real phone before you call it done. That order will save you the four hours everyone else spends debugging a template that renders nowhere.
[…] That matters more than the widget count on the box, and it is the same reasoning behind picking a lean single post layout over a template stuffed with […]
[…] The same conditions engine drives Elementor’s other templates, so if you have already built a single post layout in Elementor, this screen will look […]
[…] is also the fastest route to a custom single post layout that pulls real fields rather than placeholder text. The trade-off is a genuine learning curve: […]
[…] The Post Content widget is the important one. It renders whatever you wrote in the WordPress editor, which is what keeps your articles portable. For the design decisions inside this template we have a longer piece on building a single post layout with Elementor. […]
[…] page, you wanted a Theme Builder part and a display condition. Our walkthroughs on building a single post layout with Elementor and a blurred sticky header both live in that […]