Send Files

For information about event dates and times, see our Upcoming Events. For information about sponsorships, vendor space, parade entry, and other opportunities, see Ways to Participate. You may also find answers in our Frequently Asked Questions. If you still have questions, send a message and a team member will respond as soon as possible.

For information about event dates and times, see our Upcoming Events. For information about parade entry and other opportunities, see Ways to Participate. To register as a parade entry, read our Parade Rules and Guidelines, then use this form to register.

If you are interested in performing on stage, please read our Entertainment Policies, then submit the Entertainment Application form. If you would like more information, please see our Frequently Asked Questions or submit your question below, and a member of our team will get back to you as soon as possible.

To make a payment, or learn more about payment options, visit midsouthpride.org/pay. To make payment arrangements or for billing-related questions, send a message, and a team member will get back to you as soon as possible.

If uploading more than ten files, combine files into a single Zip archive prior to upload. If you are not sure how to create a Zip file on a particular device, see How to zip files on your computer or phone. or use an online utility like Compress 2 Go.

We're sorry you are having trouble.

Website issues are often due to conflicts with a particular browser or device. These conflicts usually sort themselves out after the next software update. In the meantime, you may be able to resolve or bypass the issue and proceed with what you were working on by following these steps:

1. Be sure your browser and operating system are up-to-date.
2. Reboot your device.
3. If you are on a mobile device, turn off your WiFi.
4. Attempt this action again using a different browser.

If you have taken these troubleshooting steps and are still having issues, please provide details about the issue and the environment you were working in when this issue first occurred: