diff --git a/js/actionCreators.js b/js/actionCreators.js
index 759468e9..7c5efc4c 100644
--- a/js/actionCreators.js
+++ b/js/actionCreators.js
@@ -339,9 +339,9 @@ export function setSkinFromUrl(url) {
   };
 }
 
-export function openFileDialog() {
+export function openFileDialog(accept) {
   return async dispatch => {
-    const fileReferences = await promptForFileReferences();
+    const fileReferences = await promptForFileReferences(accept);
     dispatch(loadFilesFromReferences(fileReferences));
   };
 }
diff --git a/js/components/MainWindow/MainContextMenu.js b/js/components/MainWindow/MainContextMenu.js
index 8d65eab2..cd375089 100644
--- a/js/components/MainWindow/MainContextMenu.js
+++ b/js/components/MainWindow/MainContextMenu.js
@@ -18,7 +18,7 @@ const MainContextMenu = props => (
     <Hr />
     <Node onClick={props.openFileDialog} label="Play File..." />
     <Parent label="Skins">
-      <Node onClick={props.openFileDialog} label="Load Skin..." />
+      <Node onClick={props.openFileDialog.bind(null, '.zip, .wsz')} label="Load Skin..." />
       {!!props.avaliableSkins.length && <Hr />}
       {props.avaliableSkins.map(skin => (
         <Node
diff --git a/js/fileUtils.js b/js/fileUtils.js
index a452a9d5..164e16ba 100644
--- a/js/fileUtils.js
+++ b/js/fileUtils.js
@@ -28,11 +28,14 @@ export async function genArrayBufferFromUrl(url) {
   });
 }
 
-export async function promptForFileReferences() {
+export async function promptForFileReferences(accept) {
   return new Promise(resolve => {
     // Does this represent a memory leak somehow?
     // Can this fail? Do we ever reject?
     const fileInput = document.createElement("input");
+    if (accept) {
+      fileInput.setAttribute('accept', accept)
+    }
     fileInput.type = "file";
     fileInput.multiple = true;
     // Not entirely sure why this is needed, since the input