MediaInfo gives a fuller and more accurate info. The framerate is probably 23.976 fps.

Yes, you should keep your project and render at the same frame rate. If your source really is 23 fps then you might want to speed it up slightly to a standard frame rate (23.976 or 24 fps), especially if it's for the web, so the web host doesn't mess it up.

Are there any cons of rendering in higher fps than the media you're using?

If resample is off then it will be very slightly stuttery. If resample is on then you will lose sharpness due to blended intermediate frames.

Lovisa, thanks for understanding. Use issues don't really consider profit in the US, anyway. I don't know how movie producers are responding to finding their stuff on YouTube these days.

My background is former AFM, ASCAP, BMI, and even a Marching Band Association!

American Federation of Musicians, American Society of Composers, Authors, and Publishers, and Broadcast Music, Inc., also Association of Concert Bands. No lip-sync at my shows!

It's a different landscape on YouTube now that Content ID gives rights holders a choice of what to do. i.e. Track, Block, Takedown or Monetize. I'm a big meanie and have all my video assets set to block, with the idea that will benefit traffic to the originals. YouTube has auto-blocked 4000 infringements for me. Maybe I should've monetized!

Anyway, it's worth understanding that some rights holders actually welcome "infringements" on YouTube because they can make money off them.

There's also the notion of derivative works of course. So someone using even Disney footage may be in the clear if they're creating something new with it.

In the latter case, I would stick with the <30-second rule per clip.

i.e. Track, Block, Takedown or Monetize.

They also have the option of doing nothing. Taking the old-fashioned approach of asking first or running full credits still garners respect with some publishers

i.e. Track, Block, Takedown or Monetize.

They also have the option of doing nothing...

= "Track"