A Shapefile is a set of companion files. Inspect the geometry, attributes, character encoding and coordinate reference before converting it. Keep the original package as the analytical source.
Inspect and convert
Confirm that .shp, .shx and .dbf belong together, and inspect the supplied CRS, commonly in .prj. A missing CRS requires source investigation; assigning one is not coordinate transformation.
ogrinfo -so -al roads.shp
ogr2ogr -f GeoJSON roads.geojson roads.shp \
-t_srs EPSG:4326 -lco RFC7946=YES
Review feature count, extent, geometry validity, identifiers and text encoding after conversion. Document field renaming and any dropped fields.
Build display tiles
For a dataset that exceeds a practical browser GeoJSON size, choose a named tile layer and zoom range. This example allows density-dependent feature dropping:
tippecanoe -o roads.mbtiles -l roads -zg \
--drop-densest-as-needed roads.geojson
Feature dropping and simplification change what is visible at particular zoom levels. Preserve the analytical GeoJSON separately and inspect the tiles at minimum and maximum zoom. An MBTiles file requires a tile-serving or conversion step; it is not itself a GeoJSON URL for a browser map.
Record the delivery
Retain commands, tool versions, CRS, source IDs, tile layer name, zoom range and distribution rights. Use the same layer name in the map style's source-layer. Check that labels and required features survive the selected zoom strategy.