Hi Matthias,

Good morning, and thanks for reaching out.

A 500 Internal Server Error during an export containing a large number of media files may occur when the server reaches one of its resource limits, such as the PHP memory limit or maximum execution time.

Could you please enable Joomla Debug and set Error Reporting to Maximum, then try the export again and share the complete error message or stack trace with us?

Also, please check your server/PHP error log for the corresponding error. This will help us determine whether the issue is caused by a server limitation or by SP Page Builder itself.

If possible, please also let us know approximately how many media files you are trying to export and their total size.

Best regards,

Did you check?

Hi, and sorry for the delayed response.

I wasn't able to get it to work. I ended up exporting the data in several batches—five posts at a time, including the media. That worked without any issues.

The total size of the media was around 80 MB across approximately 18 posts.

I’d be happy to send you the login details so you can take a look yourself?

Best regards, Matthias Wulff

Hi, and sorry for the delayed response.

I wasn't able to get it to work. I ended up exporting the data in several batches—five posts at a time, including the media. That worked without any issues.

The total size of the media was around 80 MB across approximately 18 posts.

I’d be happy to send you the login details so you can take a look yourself?

Best regards, Matthias Wulff

Hi Matthias,

Thank you for the update, and no problem about the delay.

Your test is actually a very useful clue. If five posts at a time export reliably but the full set fails, the export is almost certainly hitting a server resource limit — most likely the PHP memory limit or the maximum execution time — rather than a bug in SP Page Builder. Around 80 MB of media in a single archive is a lot for the server to process in one request.

Yes please, we will gladly take a look using the access you provided. Before we start, could you please:

1. Create a full backup of the site and database (e.g. with Akeeba Backup), and
2. Confirm that you are fine with us running a test export on the live site — it may slow the site down briefly while it runs.

As soon as you confirm, we will check your current PHP configuration and the server error log, run a test export, and report back with our findings. Please note that some of these values can only be changed by your hosting provider, so we may come back to you with a short list to forward to them.

In the meantime, your batch method is a perfectly safe workaround, so nothing is lost.

For security, we recommend changing your administrator password once we have finished.

Best regards,