If you run a BuddyPress community and you’re reading this, you’ve probably already decided rtMedia isn’t where you want to be long-term. You don’t need convincing that it’s time to move. You need to know what moving actually looks like: what happens to your members’ existing photos and videos, how much admin work this is, and whether the result is better than what you have.
MediaVerse is built for exactly this situation. It’s a front-end media plugin: members upload photos, video and audio from their own profile and activity stream, not through wp-admin, and everything stays on your own server unless you choose cloud storage in the Pro tier. rtMedia has done that same basic job for BuddyPress sites for a long time. It’s a legitimate, long-standing plugin. What’s changed is what a media community needs now: privacy that actually holds per item, a moderation queue that scales past a handful of trusted members, and storage controls so a growing site doesn’t quietly fill your disk. That’s the gap this piece covers.
What actually carries over when you move
The biggest fear with any plugin switch is losing member content. MediaVerse Pro ships a dedicated rtMedia importer built for this, so existing albums and media items don’t have to be re-uploaded by hand. The free version of MediaVerse can clean up after an import, but running the import itself needs Pro. If your community has years of member uploads sitting in rtMedia’s tables, that importer is the reason this move is realistic instead of theoretical.
Once content is in MediaVerse, it behaves differently in a few concrete ways. Privacy is set per item and per album, and that setting follows the media everywhere it appears, including inside a BuddyPress activity item. A members-only photo shown in someone’s activity feed stays members-only there too. Reported content routes into a moderation queue instead of just sitting on the profile. And your BuddyPress integration is native rather than bolted on: 11 dedicated classes cover activity content, the activity form, activity-media linkage, an activity privacy filter, sync, profile tabs, group tabs and notifications.
What you’re comparing
| Today (rtMedia) | After moving to MediaVerse |
|---|---|
| Existing albums and media items | Migrated via the Pro rtMedia importer |
| BuddyPress activity integration | 11 dedicated classes: activity content, activity form, media linkage, activity privacy filter, sync, profile tabs, group tabs, notifications |
| Gallery display | Gallery grid block, filtered by tag, category, media type or member. Four named feed layouts (Instagram, Pinterest, Flickr, Dribbble) are a Pro setting |
| Adding galleries to pages | 9 Gutenberg blocks, 14 shortcodes |
| Reported content | Moderation queue and reporting, built in on Free |
| Storage location | Stays on your own server on Free; movable to your own cloud bucket on Pro |
| Per-member storage limits | Not on Free; Pro adds per-member quotas and upload limits |
Where the layouts and blocks fit
Once the media is in place, how it’s displayed is a separate decision from how it got there. MediaVerse’s gallery grid block drops onto any page and filters by tag, category, media type or member, so you can build a members-only gallery, a public showcase, or a per-category feed without custom templates. The free grid renders every photo at its native aspect ratio rather than square-cropping it, and Pro adds four named feed layouts on top: Instagram, Pinterest, Flickr and Dribbble. That’s on top of the 9 Gutenberg blocks and 14 shortcodes available for placing galleries, uploaders and member libraries wherever you need them. See galleries and curated grids for how these pieces fit together.
The migration, step by step
- Install MediaVerse Pro alongside your existing rtMedia setup. Nothing is removed yet, so the community keeps working during this step.
- Run the rtMedia importer. It reads existing albums and media items and brings them into MediaVerse’s own structure.
- Spot-check privacy and ownership. Confirm a sample of migrated items still show the right author and the right audience, particularly anything that was members-only.
- Rebuild your gallery pages with the block or shortcodes. Set the filter you want and drop the gallery grid block where your rtMedia galleries used to live.
- Turn on the moderation queue and set reporting expectations for your moderators before you announce the change to members.
- Deactivate rtMedia once you’ve verified activity items, profile tabs and group tabs are all rendering through MediaVerse.
- If you use cloud storage or per-member quotas, configure those in MediaVerse Pro’s settings before opening uploads back up to the full community.
What doesn’t change
MediaVerse doesn’t require BuddyPress to function. If you’re running BuddyPress today, that integration stays intact and gets more specific coverage, not less: activity, profiles, groups and notifications are each handled by dedicated classes rather than a single generic hook. If you’re also running BuddyNext, MediaVerse hands its own panels and notification bell over to BuddyNext automatically, so you don’t end up with two overlapping interfaces competing for the same screen space.
Where this is a real Free vs. Pro decision
The core move, front-end uploads, albums, privacy, layouts, moderation, works entirely on the free plugin. What pushes a site to Pro is usually one of three things: the rtMedia importer itself (Pro-only), cloud storage if your server disk is a concern, or per-member quotas if you need to cap how much any one member can upload. If none of those apply yet, you can run the comparison and even test the free tier before deciding on the importer. Check free vs. Pro for the full breakdown and pricing for current plans.
Be honest about the limits
MediaVerse doesn’t run the rtMedia import on the free tier, so if budget is the only blocker, that’s worth knowing upfront rather than after you’ve committed to switching. And migrating a live community always carries some risk to metadata and display quirks that a fully scripted import can’t anticipate for every custom rtMedia setup. Test on staging first, verify a representative sample of migrated albums, and keep rtMedia installed but deactivated until you’ve confirmed the move holds up under real traffic. If your community also runs Jetonomy for forums or BuddyNext as the broader engine, MediaVerse is built to sit alongside them rather than compete, see family for how the pieces connect.