Home / Who / Who Sponsors the Fringe?

Who Sponsors the Fringe?



2017_kids 2017_visual 2017_teens 2017_recycling

2017_kids 2017_kids 2017_kids 2017_kids

2017_beer 2017_wine 2017_liquor 2017_hotel

2017_outdoor 2017_outdoor 2017_outdoor 2017_outdoor

2017_ticketing_sponsor 2017_volunteer_room 2017_volunteer_room-2 2017_volunteer_room-2

2017_volunteer_tshirts 2017_blue 2017_bronze 2017_brown

2017_gold 2017_green 2017_orange 2017_pink

2017_purple 2017_red 2017_silver 2017_yellow

Orlando Fringe provides a unique opportunity for an audience of 70,000 to meet your brand under the best possible circumstances. Your support also allows Orlando Fringe to give 100% of box office sales directly back to the artists and performers. Sponsorship is available at many levels and category exclusivity is available. Packages can be tailored to fit the marketing needs of your organization. Our fulfillment efforts ensure tangible results and a maximum return on your company’s investment. For more information and details contact sponsorship@orlandofringe.org. There is a range of sponsorships available whether you are a large corporations or a small business. We have a sponsorship package for every business and marketing budget. Please contact us for customization opportunities.

The International Fringe Festival of Central Florida, Inc. is a registered charity in the state of Florida and is registered to solicit donations.  A copy of the official registration and financial information for the International Fringe Festival of Central Florida, Inc., a Florida-based nonprofit corporation (registration no. Ch13896), may be obtained from the division of consumer services by calling toll-free 1-800-HELP-FLA (435-7352) within the state or visiting their websitehere. Registration does not imply endorsement, approval, or recommendation by the state.




Warning: Unknown: open(/data/tmp/sess_628ad582a72b0ea39d41636cfd41172b, O_RDWR) failed: File too large (27) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/data/tmp) in Unknown on line 0