Moodle 5.3

The New Long-Term Support Release

Moodle 5.3 is the next Long-Term Support (LTS) release, taking over from Moodle 4.5. In practice this is the single most important thing about it: an LTS is the version you are meant to standardise on, and it comes with a longer support window than a standard release. Instead of riding the six-month standard cycle and upgrading again shortly after, you move to 5.3, stay there, and receive bug and security fixes for years rather than months.

It is also a consolidation release. Everything introduced in the 5.0, 5.1 and 5.2 standard releases is now baked into the LTS, so an organisation jumping straight from 4.5 to 5.3 gets multi-marker grading, the modernised Question Bank, the new AI providers, the React and Composer foundations, and the routing and security work from 5.1, all at once and all supported together.

On top of that inherited feature set, 5.3 ships its own improvements, and it removes one long-standing piece of Moodle that many sites still depend on. The rest of this article covers both.

Major Advancements for Teachers and Managers

The headline changes in 5.3 focus on how people move through a course, how assessment is handled, and how the platform looks and feels day to day.

1. Linear Course Navigation

5.3 introduces sequential linear navigation controls inside course views: clear Previous and Next buttons that let a learner move through a course step by step without returning to the course index every time.

• Opt-in for course formats: third-party course formats do not display linear navigation by default; they must explicitly declare support (see the developer note below).
• Activity-level control: activity modules can override the destination of the Previous/Next controls, or step out of the navigation flow entirely.
• Predictable learner journeys: the goal is a guided, self-explanatory path through the course, reducing the "where do I go next?" friction that big courses suffer from.

2. Marking Workflows

Grading at scale gets a workflow layer: several markers can be assigned to the same submission and the final grade is computed from their marks. This builds on the multi-marker work started in 5.2 and turns it into a repeatable assessment process for larger cohorts.

• Multiple markers per submission, assigned individually or in bulk.
• Configurable grade models such as highest mark or average of all markers.
• Built for higher education and training where double-marking and moderation are the norm.

3. A Refreshed Look and Feel

The interface continues its staged redesign under the Moodle Design System. Spacing, typography, buttons and page chrome move closer to the design tokens introduced in 5.2, which means a cleaner, more consistent and more modern feel across the platform.

4. Forum Improvements

Forum discussions receive usability and navigation upgrades, including the ability to surface a "Go to all discussions" action in the sticky footer while reading a single discussion thread, so learners can move between a thread and the full forum without a detour.

A Cleaner Foundation: What Changed for Developers

For anyone maintaining themes, course formats or plugins, 5.3 carries changes worth knowing before you upgrade.

• Linear navigation API: course formats opt in by overriding uses_linear_navigation(). The \core_course\cm_info class exposes get_navigation_url(), set_navigation_url() and reset_navigation_url() so activities can steer the Previous/Next links or remove themselves from the sequence.
• Supplementary content in the sticky footer: moodle_page now provides set_supplementary_content() and get_supplementary_content(), letting any part of Moodle inject an action link into the sticky footer regardless of course format. mod_forum uses it for the "Go to all discussions" link.
• Scopes for API routes: API routes now declare their required scopes via a #[scopeset] attribute (or opt out with #[unscoped_resource]). The router validates scopes in addition to capability checks, and a core test enforces that every route declares its requirements.
• Inherited from 5.2: React in core, Composer support (mandatory in Moodle 6.0), the Moodle Design System tokens, and Open Telemetry integration.

Saying Goodbye to the Classic Theme

The most disruptive change in 5.3 is the one people overlook: the Classic theme is removed from core and moved to an external plugin. Boost becomes the only theme bundled with the LMS.

• What it means: sites running Classic, or a custom child theme based on Classic, must install the Classic theme as a plugin before or during the upgrade, or migrate to Boost.
• What to audit: theme overrides, custom CSS tied to Classic's markup and layout, and any plugin that assumes the classic navigation block or three-column layout.
• Why now: Classic was already a compatibility layer for the pre-Boost world. MoodleHQ is consolidating on Boost, so this is the release where you stop assuming Classic is present.

Everything from 5.2, Now in the LTS

Because 5.3 is the LTS, it absorbs the standard releases that came before it. If you are upgrading from 4.5, this is what you pick up in one move:

• Multi-marker assignments and a modernised Question Bank with collapsible categories, in-place renaming and the ability to move whole categories between banks.
• Clearer course design: redesigned activity pages, visible completion, explained restrictions, a sticky course title and hover cues for drag-and-drop.
• New native AI providers (Google Gemini and AWS Bedrock) with the same governance controls as existing providers.
• React and Composer in core, the first phase of the Moodle Design System, and Open Telemetry for observability.
• The 5.1 foundation: the /public directory restructure, the New Routing Engine, and expanded AI access controls.

Essential System Requirements for Moodle 5.3

Moodle 5.3 keeps the stricter requirements introduced in 5.2, so plan the infrastructure before you schedule the upgrade.

Why the Timing Matters

The 5.3 release lands on the same week that older branches reach the end of their support:

• Moodle 5.0: security fixes end 5 October 2026.
• Moodle 5.1: general bug fixes end 6 October 2026.

In other words, the moment 5.3 arrives, sites still on 5.0 and 5.1 stop receiving fixes on a version they are actively running. Moving to the new LTS is not just a feature upgrade; it is how you stay inside a support window. If your site is on an even older branch (Moodle 3.x or 4.x), the security exposure is the urgent part, and the upgrade path needs to be planned carefully.

Partnering for Success: Comprehensive LMS Service Provision

We offer comprehensive LMS services, specialising in the strategic implementation, customisation and seamless hosting of leading platforms including Moodle, Tutor and Canvas. Upgrading to Moodle 5.3 is a good moment to do it properly: we handle the infrastructure review (PHP 8.3, PostgreSQL 16), the theme and plugin compatibility audit around the Classic theme removal, the migration itself, and the new linear navigation and marking workflows. Whether you need a straight version upgrade, bespoke feature development, or robust enterprise hosting, our team ensures your platform is optimised for peak performance, security and learner engagement.