如何使用Flutter/Dart创建带密码保护的ZIP文件？

Absolutely! You can absolutely build this functionality in Flutter/Dart—even if you didn’t spot a perfect ready-made package on pub.dev. A lot of developers have tackled this before, and there are two solid approaches you can take depending on your needs:

1. Use Native Platform Tools via Method Channels #

This is the most common approach for generating standard password-protected ZIPs (the kind that work with regular unzip tools like WinZip, macOS Archive Utility, etc.). Since pure Dart packages for standard encrypted ZIPs are scarce, developers often bridge to native libraries that have proven reliability:

• Android: Use libraries like Zip4j (a popular Java library for encrypted ZIP operations). Write a simple Kotlin/Java native method that takes file paths, a password, and outputs the encrypted ZIP, then connect it to Flutter using a Method Channel.
• iOS: Use SSZipArchive (a widely used Swift/Obj-C library that supports password-protected zips). Similarly, wrap its functionality in a native method and link it to your Flutter code.

Here’s a quick example of the Dart side of the Method Channel setup:

import 'package:flutter/services.dart';

class EncryptedZipGenerator {
  static const _channel = MethodChannel('com.yourapp/zip_generator');

  static Future<String?> generateEncryptedZip({
    required List<String> filePaths,
    required String outputZipPath,
    required String password,
  }) async {
    try {
      return await _channel.invokeMethod('createEncryptedZip', {
        'files': filePaths,
        'outputPath': outputZipPath,
        'password': password,
      });
    } on PlatformException catch (e) {
      print('Error creating zip: ${e.message}');
      return null;
    }
  }
}

The upside here is that you’re leveraging battle-tested native libraries, so the ZIPs are fully compatible with standard tools. The only downside is you’ll need to write and maintain a small amount of native code for both platforms.

2. Custom Encryption + Dart’s Archive Package #

If you don’t need standard ZIP compatibility (e.g., the zip will only be used within your own app ecosystem), you can combine Dart’s archive package (for zip structure) with an encryption library like encrypt to secure file contents before zipping.

Here’s a simplified example of how this works:

import 'dart:io';
import 'package:archive/archive.dart';
import 'package:encrypt/encrypt.dart';

Future<void> createCustomEncryptedZip(
  List<String> filePaths,
  String outputZipPath,
  String password,
) async {
  final archive = Archive();
  final key = Key.fromUtf8(password.padRight(32)); // AES-256 requires 32-byte key
  final iv = IV.fromLength(16);
  final encrypter = Encrypter(AES(key, mode: AESMode.cbc));

  for (final path in filePaths) {
    final file = File(path);
    final rawBytes = await file.readAsBytes();
    // Encrypt the file content first
    final encryptedBytes = encrypter.encryptBytes(rawBytes, iv: iv).bytes;
    // Add the encrypted content to the zip archive
    archive.addFile(ArchiveFile(
      file.path.split('/').last,
      encryptedBytes.length,
      encryptedBytes,
    ));
  }

  // Write the final zip file
  final zipBytes = ZipEncoder().encode(archive);
  if (zipBytes != null) {
    await File(outputZipPath).writeAsBytes(zipBytes);
  }
}

Note: This creates a zip with encrypted file contents—not a standard password-protected zip. You’ll need to implement the corresponding decryption logic in your app to extract files later. The upside here is no native code required!

Pro Tips from Other Developers #

• Always prioritize the native Method Channel approach if you need standard ZIP compatibility—users expect to be able to open the zip with regular tools.
• If you do hunt for pub.dev packages, check out lesser-known options like zip4j_dart (just double-check the package’s maintenance status before committing).
• Don’t forget to handle platform-specific permissions: on Android, you’ll need storage access permissions, and on iOS, you’ll need to configure file access via Info.plist.

内容的提问来源于stack exchange，提问作者Toby