Frequently Asked Questions about the Transforming Oxford's Digital Communications
Tip: If you’re looking for something specific, try using your browser’s search function. Make sure the dropdowns are expanded, then press Ctrl + F (Windows) or Cmd + F (Mac) and type a keyword to jump straight to it.
Transforming Oxford's Digital Communications
How are the needs of divisions, departments and colleges being fed into the programme?
A Project Board with representation from all divisions, colleges, GLAM and the UAS is providing oversight for the programme, and its members are responsible for ensuring it meets the needs of all parts of the University. We will also be feeding feedback and insights into our work - both through the pilots, and wider engagement activities.
Who is making decisions about the programme?
The Programme Board, chaired by Social Sciences Divisional Registrar David White, reports to the Engagement and Dissemination Portfolio, Chaired by GLAM Director Richard Ovenden, which has overall responsibility for this area of work.
How will decisions be made about whether content should be on an intranet or a website?
The University's new Digital Content Strategy informs these decisions. Guidance is available on the migration webpage for the migration of existing content, and a new governance group, with representation from across the University, has been recently established to oversee the creation of new content.
What relationship if any is there between the new intranet and the external facing main University website?
The University website on Oxweb will be for external content only. Where more detailed content is available for staff and students, links will be provided through to OxIntranet. There will also be small staff and student gateways on Oxweb that link through to further information on OxIntranet.
Are there accessibility tools built into the new platforms?
Yes, accessibility is a core commitment of the programme, and all platforms will be built to the highest accessibility standards to support our users and meet compliance needs. Fresco will benefit from Sally AI checker, while OxIntranet will leverage SharePoint’s built-in accessibility checker. Oxweb, like all our platforms, already follows these highest standards, ensuring accessibility remains central to our approach.
Have the Intranet and Fresco projects considered the potential future integration of AI solutions in the platforms?
We’re looking at this closely at the opportunities for AI integration on OxIntranet, and expect to build it into the platform in the near future. We’re also building out AI-powered tools in Oxweb to support migration, metadata writing, and content review, both for the migration phase and for long-term use.
What will be happening with OxTalks and its replacement?
Oxford Events will be launching in the coming months as the replacement of OxTalks. Powered by the University’s new CRM platform, the updated events listing site, with curated calendars and streamlined event submission form, will be based on the latest and best practice technology. As well as the enhanced user experience, Oxford Events provides a new opportunity for users who had opted out of OxTalks to re-engage with the resource. Find out more at https://staff.admin.ox.ac.uk/oxford-events.
OxIntranet questions
Why do we need a new intranet when we already have SharePoint?
OxIntranet is an area of the University’s existing SharePoint platform. SharePoint has a wide range of uses, from workflow management to document storage to communications and collaboration. OxIntranet brings the intranet parts of the platform together, making it easier for staff and students to find internal information all in one place, and improving digital experience for users. There won’t be any changes to the non-intranet parts of SharePoint, so the University will continue to benefit from its functionality as well as having a compelling intranet on the platform.
Why are we focusing on intranets? Should we not be exploring AI tools instead?
AI and related tools, such as enterprise social networks, will play an important role in improving our internal communications. While our current focus is on getting the fundamentals right, including data, intranets, and email, we are also actively exploring how AI can be implemented to add further value. To make the most of AI and other advanced tools, it’s essential that our content is well structured and organised. Both humans and AI systems rely on clear, consistent information to function effectively, so investing the effort now in organising our content will ensure we can fully benefit from AI and intelligent search capabilities in the future.
How do programmes that sit outside of "Departments and Colleges" fit within OxIntranet?
This is something the project team is currently exploring. If you have an example of a cross-departmental project that you would like included on OxIntranet, please contact us to discuss it.
Currently people find my pages on google, how will users find content when we move to a locked down intranet?
At present, there is a wide range of internal content that is available on the open web. This is bad practice from an information security perspective, and makes it difficult for internal and external users to find the specific information they need. Moving all internal content to a single intranet will make it easier for internal and external users to find content that is relevant to them.
We are working to enhance SharePoint search to make searching a positive experience on the intranet, and this will be greatly helped by having all internal content in a well-managed and governed intranet. We are planning on having small staff and student gateways on the main University website, to direct staff and students to the content they need on OxIntranet. However, staff and students will not be able to use Google as a starting point as they have previously.
We aware that this is a change for many people, but we are working to ensure the transition is as smooth as possible, and that it makes content easier to find rather than more difficult.
Can any content on OxIntranet be made available to external audiences?
OxIntranet is only for staff and students with Single Sign-On credentials, and information will need to be published on the web if it is for external audiences.
If individuals need to access internal content, they will need to apply for a Virtual University Card, which will give them access to the intranet.
Will there be rules about who can request an OxIntranet site, and training to set up and maintain it?
There will be a new site approvals process for requesting OxIntranet sites, which will be reviewed by a new Web and Intranets Governance Group. Until this process is finalised, OxIntranet is open to expressions of interest for new sites. In terms of training, our Help and Support site on OxIntranet offers self-help resources for departments and colleges building their sites.
How is content governance managed for OxIntranet (e.g. if there are conflicts between multiple content items covering the same topic from shared, divisional and departmental authors)?
As Oxford is a devolved institution, there will be unique information and individual topics in different parts of the organisation, and OxIntranet has been structured to allow for this diversity.
However, we are also taking steps to encourage content owners not to duplicate content unnecessarily, and to link through to central and divisional information where possible. We will also be using individuals' identity to target content to users who it is aimed at, to ensure that information is as relevant as possible.
Who will be responsible for managing permissions/groups on SharePoint?
The OxIntranet team will have over-arching responsibility for permissions across the intranet. However, local units will be responsible for managing their own content on OxIntranet, and this includes assigning local user permissions and groups.
Our department has an sharepoint intranet already but access is limited to staff of that department only. If that intranet was linked to OxIntranet, will permissions be retained?
We encourage content on OxIntranet to be accessible to everyone with an SSO, meaning users can access content from their various University affiliations. However, visibility can be locked down to specific groups where required. The process is fairly simple for migrating an SPO intranet to OxIntranet, and existing permissions can be retained if desired.
Will there be an area for on-course students on short courses (e.g. at Oxford Lifelong Learning or SBS) who are current students but who don't have Oxford SSO accounts?
Only users with Single Sign-On credentials are able to access OxIntranet. Information for students without SSO on short courses will need to be published on local websites or alternative systems.
What if people have multiple affiliations, will they receive multiple SharePoint accesses? Or will their access be limited to only their main affiliation?
We are working with the Identity Project to ensure users get access to all the information they require, even if they have multiple affiliations
I am about to undertake a new intranet project. What should I do?
With the recent launch of OxIntranet, we’ll soon begin accepting requests for new intranet sites. In the meantime, we’re inviting expressions of interest from those considering setting up a new intranet on the platform.
If you are facing time pressure and need a new intranet site more urgently, we recommend building your intranet on SharePoint Online on a single site (not a Hub), and minimising bespoke workflows and functionality. This will make it simpler to migrate to OxIntranet in the future. Due to budgetary constraints, the level of support for local (rather than University-wide) content will be limited to self-help guides and resources during the 2025/26 academic year.
I have just carried out a migration to a new intranet, what shall I do?
We realise that new intranets are created on a rolling basis, and expect this includes those that have been very recently launched. It will be a straightforward process to move existing SharePoint intranets to OxIntranet, and we would be happy to talk to you about how and when this might take place.
If you have an intranet on a third-party platform, there is no action mandated at this stage. There is not a requirement to move at the current time - although over time there will be an expectation that new intranets are built on OxIntranet. However, if your intranet is currently on Mosaic (which is nearing end-of-life) your site will need to move sooner rather than later, supported by the programme.
My content is moving to the Intranet, can I redirect users to the correct page on the new Intranet?
We are making use of a redirect tool called Akemai to redirect users from old Mosaic sites to OxIntranet. It may be possible to give redirects to specific pages, depending on how the current Mosaic site is set up.
Which resources and support will be available for the "ongoing migration of departments and colleges to the intranet" for existing content?
In the first instance, support from the OxIntranet team will focus on UAS content migrating from Mosaic. Other units interested in joining the platform can access our dedicated Help & Support site on OxIntranet, designed to guide you through the process of joining the platform. There is also a Community of Practice group where editors on OxIntranet can collaborate and support each other.
Do we plan to address issues with mailing lists and e-newsletter distribution?
Yes. We expect that our work enhancing staff data will help address shortfalls in this area. We will also be looking at e-newsletter functionality as part of our longer-term roadmap.
I would like to know more about how the News pages are going to work on OxIntranet.
There is a dedicated News and Events area of OxIntranet, which displays news which is relevant to all staff and students. In addition, each unit onboarded onto OxIntranet will have their own local news site, for news relevant to their own staff and students. It will be possible to tag local news to appear on a 'News from across the University' area of the news. Staff and students can 'subscribe' to news which they interested in. It is possible to add news links to existing news stories on other parts of OxIntranet, and this should reduce the need to re-key internal news in multiple places.
Will it be possible to integrate any OxIntranet data (e.g. relating to profiles) into Fresco sites?
At launch, profile information on Fresco will be published on the platform, while OxIntranet data will be derived from internal systems. As such there will not be a connection between the two. However, we are exploring integrations such as via Sympletic and other University systems, so this may change in the longer term. More details will follow as this work progresses.
How will people data work to identify and target audiences?
As units are onboarded onto OxIntranet, we will work with the University's new Identity Service to integrate people data with the platform via a service called Entra ID. This means that SharePoint will have a record of a user's status, and which part of the University they are in. This will allow content to be targeted as appropriate.
Users will also be able to 'subscribe' to News that is of interest to them.
Please bear in mind that not all functionality will be available at launch, but it is something we will develop over time.
Is there a site size limit?
25 TB is the limit for a site collection. Document upload size max is 250GB.
In OxIntranet's launchpad, is there any option to build a custom module, or integrate with other open source platform like Moodle?
The launchpad is designed to give you quick access to any tools you frequently use. It does not have the ability to build or create any modules or tools. If there is a platform you use frequently you can customise your launchpad to to access this.
Is it possible to show a staff list of all people in a department?
Using the People Directory web part you can apply filters in the settings to only show staff (and students) in certain departments.
Are you using Agents as a way for users to find information on this intranet?
We are currently exploring options for using Agents and other AI solutions on the intranet and will provide more information as soon as possible.
Will there be any integration with digital signage to show OxIntranet content on internal display screens?
At present our focus is on building intranet content. However, there are opportunities to integrate this with other channels, including screens and newsletters, and this will be something we will explore as the project develops.
Is there any concern about losing some existing functionality (e.g. power automate functions like creating staff records or setting reminders to read documents)?
No - all existing SharePoint Online functionality continues to be available on OxIntranet, so this should not be an issue.
Will OxIntranet be integrated with Teams Channels?
As OxIntranet is based on SharePoint, which is part of the Microsoft suite, there is good integration with other Microsoft apps such as Teams. We are currently exploring how to make the best use of these types of integrations, and more information will follow as soon as possible.
Has a process been agreed for getting events related to projects/programmes displayed on the staff landing page Events Calendar? E.g. events taking place as part of a formal consultation?
We are currently developing a governance model for events, including how OxIntranet aligns with the new Oxford Events platform. More information will follow in the near future. In the meantime, events can be listed by contacting the relevant communications team. For the For Staff landing page, the PAD Internal Communications team.
As local site editors, will we have an opportunity to customise the look and feel of our units' homepages?
Local teams will manage the content, look and feel of their local sites, to ensure they work for their staff and students. However, in order to ensure a consistent experience across the intranet, there will be certain style and design elements that all site owners will be expected to follow. In doing so we aim to get the right balance of local ownership and a joined up user experience.
I find that Sharepoint Online loads very slowly. Can you reassure us that there won't be any performance issues with a major shift to SPO?
This has been considered and we are confident that the expected increase in traffic will not negatively impact performance. However, we will continue to monitor this, and take action if required.
Will events feed through automatically from the platform that will replace Oxford Talks?
Yes. We are working with the Oxford Talks team to integrate events from the system with OxIntranet. More information will follow about this in the near future.
Are there any plans for blogging (& automated feeds to into social media accounts)? My department uses Wordpress to blog about news of resources, services, which are public facing.
It is technically possible to feed external content into SharePoint Online and this can be done locally. However, OxIntranet is focused on current staff and students, and we would only recommend surfacing content that is specifically relevant to internal groups rather than duplicating all external content internally. This will ensure the intranet stays as relevant as possible to our staff and students.
What analytics tools have been installed on OxIntranet to analysis user behaviour?
Google Analytics has been installed, in addition to out of the box SharePoint analytics. We also plan to install Microsoft Clarity to add additional insights about user behaviour.
Fresco web CMS questions
I hear Mosaic is going out of support in 2026. What does this mean and is my current website secure to use until then?
End of life support means the software or system will no longer receive updates, including security patches, from the third party supplier. In the mean time, your Mosaic site will continue to be operational and secure.
Will all Oxford websites need to move to Fresco, the new Content Management System (CMS)?
The strategic ambition is for Fresco to be the web platform used across the collegiate University, so as to achieve a coherent user experience and drive down costs of web expenditure. As a result, the aim is, over time, for all parts of the University to move to Fresco, the new CMS. The initial focus (during 25/26) is on the sites that are currently on Mosaic (due to the end-of-life deadline to move off Mosaic) but all parts of the University will be encouraged to join over time - from 26/27 onwards - including for new sites (see the question in relation to the timelines for the availability of new sites).
I manage a website on a platform besides Mosaic (eg. Haiku) - should I move to Fresco?
The strategic ambition is for Fresco to be the web platform used across the collegiate University so as to achieve a coherent user experience and drive down costs of web expenditure. As a result, the aim is that over time, all parts of the University will move to Fresco, the new CMS. However, the initial focus (during 25/26) is on the sites that are currently on Mosaic, due to the end-of-life deadline to move off Mosaic, and so sites on other platforms are not mandated to migrate at this stage. Once this initial goal has been achieved, we hope to be able to support the migration of sites from other platforms.
Will departments and colleges all be required to move to Fresco in the long term? Or is it optional?
Migrating sites from Mosaic is the current priority. If a unit is seeking a new CMS (for example, because their current platform is reaching end of life), Fresco will be the recommended option and requests for new sites on Mosaic will be required to demonstrate that Fresco cannot meet their needs. However, we recognise Fresco may not yet meet every requirement within the timescales some units need, so it will not be mandatory at this stage.
If I manage a standalone website, will I be required to migrate, and where to?
Unless there is a clear reason not to maintain a standalone presence, any existing standalone sites on Mosaic are expected to be migrated to Fresco on a like-for-like (site-for-site) basis. A number of Fresco templates are available for this, including the departmental template, templates for closely affiliated sites, and the microsite template.
As part of the migration, sites will be expected to adopt the relevant Fresco template and configure available options (e.g. colours) to ensure a coherent user experience across the University’s web estate. For departmental websites, a recommended information architecture is also available; while it will not be applied automatically, its use is strongly encouraged. Please note that within UAS, our direction of travel is to consolidate content into OxIntranet and Oxweb, with a smaller number of standalone sites overall.
How will it be decided which research groups get standalone Fresco websites?
Existing websites will be migrated as is. The default location for new programmes, institutes, and externally facing units is a dedicated subpage(s) within the website of the responsible department. For more information, please see the new site request information pages.
Is it just a recommendation or are you insisting that 'programme' websites migrate to Fresco? e.g. a fixed-term funded research programme attached to a department but that doesn't offer teaching.
Nothing mandatory, see content strategy for long term desire to consolidate all university pages onto a single platform for the benefits of cost, efficiency, user experience
Which version of the Drupal is Fresco going to run on?
Fresco is currently built on Drupal 10 with a plan to upgrade to Drupal 11 in 2026.
Is it possible to know what functionality will NOT be available on Fresco? We have researchers continuing to make new pages, but if image carousels (for example) won’t be supported on Fresco, we’d like to know now.
The Fresco roadmap is constantly evolving and new components are being added all the time. There are a few components not being migrated to Fresco - some are being consolidated into another component in Fresco or have a suggested alternative, others will have no alternative in Fresco. Guidance will be provided on the migration team webpage once published.
We are concerned about the changing web address and the associated issue of having to re-design and re-print physical material. This will create further workload and will have a financial impact on our outreach event. Can the re-direct be in place longer? Or is there a way to keep our web address?
There will be some scope for exceptions to the redirect policy. Details are yet in discussion, but these exceptions could possibly be permanent for a limited number of sites. This will apply to those sites with printed materials or widely publicised addresses that have existed in publications for many years. Please note that departments, divisions and GLAM sites have a custom domain name so are unaffected by the redirect policy).
Will there be training and support for setting up Fresco when it is ready ?
Yes. The Migration Toolkit and the Fresco team have support documentation and how-to videos. Online training sessions will also be available to support content owners migrating, and a new Teams community channel will be created for content editors on Fresco.
If you are a new content editor, we are developing the training to guide you through the end to end process.
Will Fresco make use of Symplectic Elements for integrating publication data?
The Publications Listing widget in Mosaic draws publicly available publications metadata from Symplectic Elements and outputs these results (such as publication date, abstract, journal issue, etc) in a pre-set listing style. Development is underway in Fresco to enable functionality in new sites, estimated to be available by Easter 2026.
A survey has been sent out to current site users of the Mosaic Symplectic widget, aimed at gathering what functionality is use and what users would like to see in the future. If you haven't received this and would like to input into the process, please contact ralph.watson@it.ox.ac.uk
What tools will be available to new Fresco sites for tracking user behaviour?
Site Owners will be able to implement Google Analytics 4, Microsoft Clarity, and other approved analytics tools, provided they are GDPR-compliant and respect user's privacy and consent preferences and support for setting up these tools is available. Contact Theo Ratcliff (Web Experience Manager) for more information.
Is Fresco available for new sites?
Fresco is now accepting new site requests via the newly established request process. As part of our aim to streamline content across the University and improve the user experience, those requesting websites on either either Fresco or Mosaic will now need to seek approval from a Web and Intranet Governance Group, which includes representation from across the collegiate University.
The Governance Group will determine whether Fresco or Mosaic would better serve the needs of the request, and although Fresco is now the preferred platform where possible, we understand that functionality and design elements are developing over time, and therefore Mosaic sites may be provisioned where necessary. Learn more about the new site request process.
Would there be training for the staff who are expected to make changes or set up new sites on Fresco?
Yes - details of the plans for content editor training will be published in due course. We anticipate that there will be a mix of documentation, classroom sessions and short topic based videos.
Will there be support specifically provided to help design new sites, from an agency or internally? Where sites do need to have a more customised design/layout, we will need support to align this all with our brand guidelines.
Although the current priority for the programme is migrating existing sites, please do email Theo Ratcliff, our Web Experience Manager, if you'd like to discuss how best to approach design on your new site.
Migration questions
When do I need to migrate my site?
The University's current web platform, Mosaic, will be end-of-life in October 2026 meaning that all content needs to be migrated off Mosaic before that deadline. All Mosaic site owners have been contacted with their migration month start date. If you have not received an email and are expecting to migrate your site, please email the Migration Support Team.
What do I need to do before my migration window?
Before your site is migrated, you should prepare your website for migration by following the Pre-Migration Checklist published by the Migration Project. This guide includes essential and recommended actions to help make your migration run as smoothly as possible.
What is the auto-migration tool?
The programme has developed an automation tool that will copy content (text, images, attachment files etc.) across from Mosaic sites to new Fresco sites. The tool will significantly speed up the time required to migrate sites from Mosaic to Fresco and will remove the need for time-consuming manual migration. The tool will rebuild the website into a format that is as close to possible as the Mosaic site in alignment with the feature set of Fresco (which is not identical to that of Mosaic). The auto-migration process will be managed by the migration support team before sites are handed over to site owners for reviewing, editing, and finalising prior to go live. The migration toolkit website contains a guide on which features will be migrated to Fresco.
Note that Fresco sites will be expected to use the Fresco design system in relation to choice colour, recommended information architecture etc. so that there is a coherent user experience for end users of the University's websites. Advice and guidance will be provided to support you with moving to this new design system after the auto-migration process has taken place.
How has the auto-migration tool’s capabilities been tested? Is there anything the tool cannot auto-migrate?
The auto-migration tools has been regularly tested against a variety of live Mosaic websites. There are a number of Mosaic capabilities that are not supported in Fresco. When the auto-migration tool encounters one of these, the content will be copied across but will be placed on the page in an area where it can be further styled into a Fresco component. The auto-migration tool is regularly being updated in line with newly added Fresco functionality, and the Migration Toolkit offers a comparison list of Mosaic to Fresco functionality.
Will there be a time period where the new website can be modified to ensure it is suitable for use prior to the Mosaic site becoming obsolete?
Once the auto-migration of your website content from Mosaic to Fresco has completed, you will need to review and update your new Fresco website before making it public in place of your Mosaic site. We will encourage you to complete the review as quickly as you can to avoid having to maintain two websites in parallel. Once the new site is published on Fresco, redirects will be applied and the old Mosaic site will be decommissioned.
What support is available for migration?
Migrators will be invited to attend a migration kickoff session at the start of their move, outlining details of the process, and provide introductory training. The programme is taking an auto-migration approach for Mosaic to Fresco migration so that the majority of the migration work is completed automatically. Site owners will then be expected to review, update, and finalise context. In addition, the programme has a migration toolkit website containing advice and guidance for the migration. Plus, there will be some support available from a migration support team where needed. A different approach is being taken within the UAS, where content is migrating to OxIntranet and Oxweb. Specific support arrangements will be communicated to UAS teams.
Is direct support from the migration team only offered to sites currently on Mosaic?
The priority is with sites currently on Mosaic, due to it approaching end of life. Therefore, the migration team are currently only supporting sites migrating off Mosaic over to Fresco. The Fresco team will be able to support new sites being built on Fresco.
Will there be training and support for setting up Fresco when it is ready ?
Yes. The migration team have a toolkit website in development and the Fresco team have support documentation and how-to videos. Online training sessions will also be available to support content owners migrating, and a new Teams community channel will be created for content editors on Fresco.
If you are a new content editor, we are developing the training to guide you through the end to end process.
We have physical items (banners, signs, posters) that includes the web address. Is it possible to increase the time the web address will redirect to the new fresco site? We will need to redesign and reprint items.
There will be some scope for exceptions to the redirect policy - details are currently in discussion, but these could possibly permanent for a limited number of sites. This will apply to those sites with printed materials or widely publicised addresses that have existed in publications for many years. Please note that note that departments, divisions and GLAM sites have a custom domain name so are unaffected by the redirect policy.
If my current website is data heavy and outdated, is it possible to build a new one straight into Fresco without a transition from Mosaic (even if this takes longer)?
We still need to migrate your existing website to Fresco. Once migrated you can chose to republish the original migrated content or to build up a new site on Fresco.
Will my website address stay the same?
This depends on whether you are using the default Mosaic platform address structure, e.g. <sitename>.web.ox.ac.uk or whether you have requested a custom domain e.g. <sitename>.ox.ac.uk or <sitename>.org.uk.
If you have a Mosaic website that is only using the default Mosaic platform supplied address structure then your website will be given a new address on Fresco of <sitename>.site.ox.ac.uk. After you publish your new website on Fresco there will be a temporary redirect from your <sitename>.web.ox.ac.uk to your new <sitename>.site.ox.ac.uk address for four months. After this period, users navigating to your old Mosaic address will see a page not found error. We will ensure that search engines are notified that a site has been moved so users are able to find the website through search engines.
If your website uses a custom domain, this will be maintained when the website is migrated to Fresco. The custom domain name will need to be added to the site settings of the migrated website and the Fresco team will update the routing to point to the new site when it is ready to go-live.
I cannot remember how to scan our website for total pages. Could you remind me how to do it please?
You can view website statistics via the link on Site Details page. Follow this link to find out how to do that.
If my website is not being migrated onto Fresco, is there anything I need to do to decommission the website. How long will I have?
The Migration Project has a record of sites which Site Owners have told us do not need to be migrated. We will be contacting those sites to confirm that decision. If you are not sure if you have told us, please feel free to contact the team. Unless you request otherwise, the website will remain live until the Mosaic platform is decommissioned around October 2026. If you would like your website to be unpublished before then, please complete this form to request site deactivation: https://oxfordmosaic.web.ox.ac.uk/contact#tab-2640091
How can I reduce the storage size of my website to make it more environmentally sustainable?
Reduce the resolution of images which are likely too big. People profile pictures can be in the range of 30-100KB, aim for 50-60KB and still appear high resolution. Images of around 2MB, are up to 10-40 times larger than they need to be, ideally they should be around 50-100KB for large full width images. As an example: the main image on this page https://www.theguardian.com/artanddesign/2025/may/28/v-and-a-east-storeh... is only 53KB. You can see that it is still a high quality image but is in the AVIF format not older formats like JPG or PNG.
Convert images to newer web friendly formats like webp and AVIF that reduce file size and keep resolution. A 2.1MB PNG file can be converted to an AVIF file as an 86KB file of the same dimensions. There are online image file format conversion websites.
Delete images uploaded to the site that are no longer needed, they count towards your storage even if not being used
Delete draft pages if no longer needed
Delete published pages if no longer needed
