
Nextcloud 28 is a major release that brings many exciting features to the table. It's designed to improve user experience and security.
One of the key highlights of Nextcloud 28 is the introduction of a new admin dashboard. This dashboard provides a more streamlined and intuitive way to manage your Nextcloud instance.
The admin dashboard is designed to help administrators quickly identify and resolve issues, making it easier to keep your Nextcloud instance running smoothly.
Related reading: Watch Dateline Season 28 Episode 1
New Features
Nextcloud 28 brings a host of exciting new features to enhance your experience.
One of the standout features is the improved performance of Nextcloud Hub, which now loads 2.5 times faster than before.
A new feature in Nextcloud 28 is the introduction of Nextcloud Talk's live streaming capabilities, allowing you to broadcast to a large audience.
With Nextcloud 28, you can now access your files from any device with a new mobile app, available for both iOS and Android.
Explore further: 5 Key Features of Dropbox
LibreOffice Office File Previews

With Nextcloud 28, you can generate previews for Office files using LibreOffice.
This feature allows you to view a preview of Office files, such as Word documents or Excel spreadsheets, directly within Nextcloud.
Until Nextcloud 28, a single LibreOffice user profile was used to generate previews, which could lead to preview generation failures if multiple previews were created at the same time.
With Nextcloud 28, a different LibreOffice user profile is used for each file, which can result in a large number of LibreOffice invocations if you upload many files.
However, you can use the configuration options preview_concurrency_new and preview_concurrency_all to limit the number of previews generated concurrently, if php-sysvsem is available.
Previews for EMF files can be enabled without a local LibreOffice installation if you're using Nextcloud Office / Collabora, starting with Nextcloud Office 8.3.0.
To enable EMF file previews, add 'OCA\Richdocuments\Preview\EMF' to enabledPreviewProviders.
Check this out: Add Dropbox Google Drive Office 2013 Windows 10
Added APIs
The new Files app has been optimized to load faster, but you might encounter some race conditions if you're using the old `Util::addScript` method to load custom properties. Instead, use the new `Util::addInitScript` method to load your scripts right after the common core scripts and before the Files app.
Take a look at this: Nextcloud Migrate to New Server
If you need to register file actions, you should use the dedicated API from https://npmjs.org/@nextcloud/files or https://nextcloud-libraries.github.io/nextcloud-files/functions/registerFileAction.html.
To register entries in the new file menu, use the dedicated API from https://npmjs.org/@nextcloud/files or https://nextcloud-libraries.github.io/nextcloud-files/functions/addNewFileMenuEntry.html.
When interacting with the Files app router, use `OCP.Files.Router`.
Here are some key APIs to keep in mind for the Files app:
Changes and Removals
OC.loadScript and OC.loadStyle have been removed, and you should use OCP.Loader instead.
Several APIs have been removed, including OC.appSettings, OCA.Files (except for Sidebar and Settings), and OCA.Files_Sharing. You can find replacements in the Added API section.
If you were using the following events, you'll need to switch to the new ones:
- OCP\AccountManager::userUpdated is now OCP\Accounts\UserUpdatedEvent
- OCP\IDBConnection::ADD_MISSING_COLUMNS is now OCP\DB\Events\AddMissingColumnsEvent
- OCP\IDBConnection::CHECK_MISSING_COLUMNS is now OCP\DB\Events\AddMissingColumnsEvent
- OCP\IGroup::postAddUser is now OCP\Group\Events\UserAddedEvent
- OCP\IGroup::postDelete is now OCP\Group\Events\GroupDeletedEvent
- OCP\IGroup::postRemoveUser is now OCP\Group\Events\UserRemovedEvent
- OCP\IGroup::preAddUser is now OCP\Group\Events\BeforeUserAddedEvent
- OCP\IGroup::preDelete is now OCP\Group\Events\BeforeGroupDeletedEvent
- OCP\IGroup::preRemoveUser is now OCP\Group\Events\BeforeUserRemovedEvent
- OCP\IUser::changeUser is now OCP\User\Events\UserChangedEvent
- OCP\IUser::postDelete is now OCP\User\Events\UserDeletedEvent
- OCP\IUser::postSetPassword is now OCP\User\Events\PasswordUpdatedEvent
- OCP\IUser::preDelete is now OCP\User\Events\BeforeUserDeletedEvent
- OCP\IUser::preSetPassword is now OCP\User\Events\BeforePasswordUpdatedEvent
- OCP\Share::preShare is now OCP\Share\Events\BeforeShareCreatedEvent
- OCP\Share::preUnshare is now OCP\Share\Events\BeforeShareDeletedEvent
- OCP\Share::postAcceptShare is now OCP\Share\Events\ShareAcceptedEvent
- OCP\Share::postShare is now OCP\Share\Events\ShareCreatedEvent
- OCP\Share::postUnshare is now OCP\Share\Events\ShareDeletedEvent
- OCP\Share::postUnshareFromSelf is now OCP\Share\Events\ShareDeletedFromSelfEvent
- \OCP\Collaboration\Resources::loadAdditionalScripts is now OCP\Collaboration\Resources\LoadAdditionalScriptsEvent
Removed APIs
The Removed APIs section of the changes and removals is a crucial part of understanding what's no longer supported in the new version. Here's what you need to know:
OC.loadScript and OC.loadStyle have been removed, so you'll need to use OCP.Loader instead. This change affects how you load scripts and styles in your application.
You might enjoy: Do I Need Onedrive on My Android Phone

OC.appSettings has been removed, and there's no replacement available. This means you'll need to find an alternative way to handle app settings.
OCA.Files has undergone significant changes, and everything except Sidebar and Settings has been removed. The Added API section provides more information on replacements for the removed functionality.
Here's a list of the removed APIs:
- OC.loadScript and OC.loadStyle: Use OCP.Loader instead.
- OC.appSettings: There is no replacement.
- OCA.Files: Everything removed but Sidebar and Settings. See the Added API section for replacements.
Updated Core Libraries
If you're an app developer, it's essential to check your code for incompatibility with updated core libraries.
The update of core libraries should have little to no effect on apps that use only official public APIs of Nextcloud.
However, there are some edge cases where an app still has a code dependency to a library shipped with Nextcloud.
App developers are recommended to check their code for any incompatibility, especially when 3rdparty classes or functions are used.
Moreover, it's recommended to check compatibility with sophisticated tools, as documented at the static analysis section.
Recommended read: Google Drive Qr Code
Long Term Support
If you're running Nextcloud for an organisation-critical use case, you could consider upgrading your subscription to a premium subscription.
This comes with 5 years of long term support, which means you continue to receive maintenance releases for high and critical security issues.
System Requirements
To run Nextcloud 28 smoothly, you'll want to ensure your system meets the minimum requirements. A 64-bit CPU, OS, and PHP are necessary for optimal performance.
Nextcloud can run on 32-bit systems, but be aware of the limitations: dates before 1970-01-01 and after 2038 are not supported.
You'll also need sufficient RAM to handle the demands of your Nextcloud server. A minimum of 128MB RAM per process is required, and we recommend at least 512MB RAM per process for a smoother experience.
In low memory environments, some features or apps might need adjustments to their default settings or be disabled altogether. To use the built-in Updater, you'll need at least 256MB of RAM.
CPU and OS
To ensure Nextcloud runs smoothly, you'll want to make sure your CPU and OS meet certain requirements.
A 64-bit CPU is necessary for optimal performance.
You'll also need a 64-bit operating system (OS) to run Nextcloud without issues.
You might enjoy: Google Drive App for Mac Os
A 64-bit OS will give you the best experience, but 32-bit systems are supported, albeit with some limitations.
If you're using a 32-bit system, keep in mind that dates before January 1, 1970, and after January 1, 2038, are not supported.
Here's a quick rundown of the limitations on 32-bit systems:
- Dates before January 1, 1970, are not supported
- Dates after January 1, 2038, are not supported
Memory
Memory requirements for running a Nextcloud server are greatly variable, depending on the numbers of users, apps, files and volume of server activity. This means you'll need to allocate sufficient RAM to ensure smooth performance.
A minimum of 128MB RAM per process is needed, and we recommend a minimum of 512MB RAM per process. This is essential for Nextcloud to function properly.
In low memory environments, some features or apps may require adjustments to their default settings in order to function. This might mean tweaking settings or disabling certain features to prevent crashes.
To use the built-in Updater, at least 256MB is required. This is a critical feature for keeping your Nextcloud server up-to-date and secure.
Recommended read: Google Drive Free Storage Space
Database Requirements for MySQL
So you're setting up Nextcloud with a MySQL database, huh? Make sure you're using the InnoDB storage engine, as MyISAM is not supported.
You'll also need to set the transaction isolation level to "READ COMMITTED" - this is crucial for a smooth operation.
To avoid any issues, disable or configure Binary Logging to use ROW format. This will save you some headaches down the line.
If you want to support emojis, you'll need to enable 4-byte UTF8 support in MySQL.
Here's a quick rundown of the database requirements:
- InnoDB storage engine
- “READ COMMITTED” transaction isolation level
- Disabled or BINLOG_FORMAT = ROW configured Binary Logging
- Enabled 4-byte UTF8 support
Sources
- https://nextcloud.com/changelog/
- https://docs.nextcloud.com/server/latest/admin_manual/release_notes/upgrade_to_28.html
- https://docs.nextcloud.com/server/latest/developer_manual/app_publishing_maintenance/app_upgrade_guide/upgrade_to_28.html
- https://endoflife.date/nextcloud
- https://docs.nextcloud.com/server/latest/admin_manual/installation/system_requirements.html
Featured Images: pexels.com